Website audit · Sample report
Search, AI readiness, speed, accessibility, design and conversion, measured and compared with the four web designers that rank first for “web design Dover”.
rgleeson.com, out of 100Competitor average
01
In short
The site is well built: every AI crawler can read it, it passes almost every accessibility check, and on desktop it's as fast as anything in the comparison. It scores 84 against a competitor average of 68, the highest of the five. But it isn't being found. It's missing from the top 20 for “web design Dover” while all four competitors are in the top 4, the Google listing's name belongs to another business, and on a phone the main content takes 3.5s to 5.4s to appear. Those three are where the work is.
02
The four competitors are the four web designers that hold positions 1 to 4 for "web design Dover" in the search snapshot below. In a client's report they are named, with screenshots. This sample is public, so they are labelled A to D and their screenshots are left out.
In short
rgleeson.com scores 84, 16 points above the competitor average. It leads on AI and agent readiness, accessibility, design and visual quality, and trails on search visibility, where every competitor outranks it. Competitor C is the one to beat: fast, clear, and showing its reviews.
| Site | AI 20% | Search 20% | Speed 15% | Accessibility 15% | Design 10% | Content 10% | Trust 10% | Overall |
|---|---|---|---|---|---|---|---|---|
| rgleeson.com | 100 | 65 | 76 | 99 | 78 | 85 | 80 | 84 |
| Competitor A | 60 | 93 | 67 | 65 | 58 | 47 | 69 | 68 |
| Competitor B | 50 | 83 | 55 | 38 | 55 | 75 | 34 | 57 |
| Competitor C | 85 | 75 | 100 | 68 | 73 | 90 | 79 | 81 |
| Competitor D | 60 | 90 | 62 | 70 | 53 | 42 | 54 | 65 |
| Label | What it is | Position for “web design Dover” | Built with |
|---|---|---|---|
| Competitor A | website builder (Gridbox), Dover | 1 | Powered by Website Builder Gridbox |
| Competitor B | WordPress studio, East Kent | 4 | WordPress 7.1.4 |
| Competitor C | agency, Dover, static site | 2 | Static, on Netlify |
| Competitor D | WordPress freelancer, Dover | 3 | WordPress 7.1.4 |
03
Where the site appears for the searches a local customer would make, and whether its pages are set up to rank.
In short
The pages are technically sound: every canonical correct, one h1 each, a clean sitemap, no broken internal links. The problem is that the site doesn't appear for any of the local searches tested. The brand search is worse: “RG Web Design Dover” returns a different business called RG Web Design, in Sussex, as result 1.
| Search | rgleeson.com | A | B | C | D |
|---|---|---|---|---|---|
| “web design Dover” | Not in top 20 | 1 | 4 | 2 | 3 |
| “website designer Dover Kent small business” | Not in top 20 | 1 | 2 | 3 | 6 |
| “web design Dover Kent small business website designer” | Not in top 15 | 1 | 2 | 3 | 9 |
| “RG Web Design Dover” | Not in top 10 | 2 | 9 | 3 | 6 |
| “AI readiness website audit UK” | Not in top 20 | — | — | — | — |
| Check | Result |
|---|---|
| Titles | 25 of 32 within 60 characters; 7 post titles run long (F6) |
| Meta descriptions | 17 of 32 within 160 characters; 15 run long, including Web Services at 189 (F6) |
| Canonicals | 32 of 32 correct |
| One h1 per page | 32 of 32 |
| Heading order | 0 of 32 without a skipped level (F9) |
| Structured data | 16 of 32 pages (F7) |
| Sitemap | 32 URLs, all returning 200, declared in robots.txt |
| Internal links | 32 distinct, 0 broken, 0 redirecting, 0 orphan pages |
| External links | 18 distinct, all working when re-checked by hand |
| Redirects | www and https in one hop, except http://rgleeson.com, which takes two (F12) |
04
Whether ChatGPT, Claude, Perplexity and Google can read the site, and whether an AI agent could use it on someone's behalf.
In short
This is the site's strongest area. All the text is in the HTML, every crawler gets the real page, and the interface passes the agent-friendly checks on every page. Two competitors look open in their robots.txt but turn GPTBot away at the server, so they're invisible to ChatGPT without knowing it. What's missing here is an action an agent can take: there's no way to book (F5).
| Site | robots.txt | Fetched as GPTBot | Words in raw HTML | llms.txt | Structured data |
|---|---|---|---|---|---|
| rgleeson.com | ✓ Allows | ✓ Same page | 971 | ✓ Yes | ✓ ProfessionalService |
| Competitor A | ✓ Allows | ✕ Refused (429) | 804 | ✕ No | ✓ LocalBusiness |
| Competitor B | ✓ Allows | ✕ Connection dropped | 1,127 | ✕ No | ✓ Yes |
| Competitor C | ✓ Allows | ✓ Same page | 1,012 | ✕ No | ✓ Organization |
| Competitor D | ✓ Allows | ✓ Same page | 613 | ✕ No | ✕ No |
| Page | Words in raw HTML | Words a visitor sees |
|---|---|---|
| / | 321 | 233 |
| /websites.html | 972 | 955 |
| /audit.html | 437 | 426 |
| /contact.html | 125 | 117 |
| /project-action-carpets.html | 777 | 759 |
| /post-website-invisible-to-ai.html | 1,127 | 1,118 |
05
Lighthouse lab tests on a simulated mid-range phone on a slow 4G connection, and on desktop. Lab numbers, because the site has too little traffic for Google's real-user data.
In short
On desktop the site is quick: 93 to 99 on every page. On a phone it's slow to show its main content: 3.5s to 5.4s, against Google's 2.5s. The pages are light; the delay comes from what has to load before anything paints (five servers for two fonts and the page) and from the fade-in animation on the first screen. A half-day fix (F3).
rgleeson.comCompetitorsGoogle's “good”: 2.5s
| Page | Score, phone | Score, desktop | Main content, phone | First paint, phone | Layout shift | Weight | Requests |
|---|---|---|---|---|---|---|---|
| Home | 84 | 99 | 3.7s | 3.0s | 0.040 | 671 KB | 18 |
| Web Services | 81 | 98 | 4.0s | 3.1s | 0.001 | 505 KB | 18 |
| AI audit | 75 | 93 | 4.8s | 3.3s | 0.000 | 306 KB | 14 |
| Work | 90 | 99 | 3.5s | 1.6s | 0.022 | 864 KB | 21 |
| Action Carpets case study | 80 | 99 | 4.2s | 3.2s | 0.000 | 392 KB | 17 |
| Journal post | 72 | 99 | 5.4s | 3.5s | 0.000 | 404 KB | 16 |
| Site | Total | Images | Scripts | Fonts | Other | From other servers |
|---|---|---|---|---|---|---|
| rgleeson.com | 505 KB | 202 | 163 | 109 | 31 | 53% |
| Competitor A | 739 KB | 222 | 293 | 157 | 67 | 27% |
| Competitor B | 1,833 KB | 757 | 640 | 193 | 244 | 18% |
| Competitor C | 266 KB | 190 | 1 | 34 | 40 | 0% |
| Competitor D | 1,458 KB | 706 | 341 | 344 | 68 | 33% |
06
The same checks an AI agent depends on: contrast, names, labels, landmarks and tap targets, measured on the rendered page.
In short
Close to clean. Lighthouse scores 98 on every page; the only items it raises are the footer headings skipping a level (F9). Across the site, six links are a few pixels under the 24px tap target (F10). One competitor fails contrast on 101 of 131 text elements, mostly orange on white.
| Site | Lighthouse, phone | Text failing contrast | Small targets, phone | Images without alt | Main and skip link |
|---|---|---|---|---|---|
| rgleeson.com | 98 | 1 of 141 | 0 | 0 | ✓ Yes |
| Competitor A | 90 | 4 of 36 | 0 | 0 | ✕ No main |
| Competitor B | 76 | 101 of 131 | 82 | 2 | ✕ No main |
| Competitor C | 96 | 16 of 155 | 11 | 0 | ✓ Yes |
| Competitor D | 79 | 0 of 55 | 22 | 0 | ✕ No main |
rgleeson.com's one contrast failure is the decorative “·” between a name and a job title (#D0D0D0, 1.54:1). Across 15 pages, a separate contrast audit on 4 November measured 2,832 text elements with 10 failing, all of them minor.
07
Colour, type and layout, measured from the rendered page and then reviewed by eye at 1440 and 375px.
In short
A disciplined system: one accent colour, two typefaces (plus a monospace in one illustration), consistent components, comfortable body text. It has the top design score by the rules, but by eye Competitor C's page is the stronger one: bolder type and proof in the first screen. Four things would lift it: more of the text in ink rather than grey, fewer stray type sizes, proof in the first screen, and showing the first screen without waiting for an animation.
#0F1014Headings, primary text, dark bands21% of text · 9% of the page19.01:1 on white#5C5C5CBody and supporting text60% of text6.69:1 on white#6A7185Labels and captions1% of text4.87:1 on white#D04205Buttons, links and labels1% of text · 5% of the page4.70:1 on white#F36435Large display words, accents on ink3.14:1 on white#F9FAFFAlternate section background84% of the page1.04:1 on white#FFFFFFPage and card background6% of text1.00:1 on white#E2E2E2Dividers and card edges1.30:1 on whiteShare of text is by characters; share of the page is by pixels in a full-page screenshot at 1440px. The accent covers 5% of the page: enough to lead the eye, not enough to tire it.
Each bar shows the main colours by area, photos included, with the typefaces alongside. Competitors A and D get most of their colour from stock photos; B from orange text.
| Site | Typefaces | Sizes in use | Body size / line height | Characters per line | Headline |
|---|---|---|---|---|---|
| rgleeson.com | Inter, Cabinet Grotesk, ui-monospace | 14 | 16px / 1.6 | 47 | 80px |
| Competitor A | Montserrat | 9 | 19px / 1.6 | 49 | 65px |
| Competitor B | Roboto Condensed, Exo | 8 | 16px / 1.7 | 106 | 36px |
| Competitor C | Archivo | 16 | 16px / 1.6 | 97 | 108px |
| Competitor D | Open Sans, Poppins | 12 | 15px / 1.59 | 51 | 60px |
Type sizes on Web Services, by share of text. Grey bars carry under 3% each.
Four questions, 0 to 5 each: is the hierarchy clear (one thing to read first, one thing to do)? Are colour, type and components used consistently? Do the images show the actual business and its work? Would you remember it next to the others? Scored from the first screen and a full scroll at 1440 and 375px.
| Site | Hierarchy | Consistency | Imagery | Distinct | Total /20 | Notes |
|---|---|---|---|---|---|---|
| rgleeson.com | 4 | 5 | 3 | 3 | 15 | Clear headline, one accent colour used sparingly, every component from one system. The first screen has no picture of real work and no proof, and the layout reads like many well-made studio sites. |
| Competitor A | 2 | 2 | 1 | 2 | 7 | A stock photo of a woman making goggles with her fingers fills the first screen under a purple-to-blue gradient; the cookie banner covers the call to action. |
| Competitor B | 1 | 1 | 2 | 2 | 6 | Seven-item navigation, a clip-art logo, three typefaces and body lines over 100 characters long. A photo of Dover's guns is local, but doesn't show the work. |
| Competitor C | 5 | 5 | 3 | 4 | 17 | Huge, confident type, two calls to action and a proof bar (5.0 on Google, 65 reviews) in the first screen. The strongest page of the five. |
| Competitor D | 3 | 2 | 1 | 1 | 7 | A stock close-up of an eye behind the headline; "Website Design in Dover" repeated as the h1, h2 and h3. A standard theme with little changed. |
60% of the characters on Web Services are muted grey #5C5C5C and 21% ink #0F1014. The grey passes contrast at 6.69:1 on white.
Do: Keep grey for supporting text, but set the opening paragraph and card descriptions in ink. Contrast between levels is what makes the hierarchy, and right now most text sits on the second level.
Text on Web Services uses 14 sizes from 12 to 80px; five of them (12, 14, 17, 32 and 52px) carry under 3% of the text each.
Do: Fold the stray sizes into the nearest step of a 9-step scale (13, 15, 16, 20, 24, 32, 44, 64, 80) and name each as a token, so new pages can't add more.
The first screen at 1440 and 375px has a headline, a paragraph and the enquiry form. The one testimonial is halfway down the page.
Do: Add one line of proof under the headline: a client result ("Vancat: sales up 200%") or, once there are enough, the Google rating and review count.
Sections start at opacity 0 and fade in as they scroll into view; the hero headline fades in word by word. Lighthouse counts the page as painted only once that finishes.
Do: Show the first screen without any reveal, and keep the fade for content further down. This is part of finding F3.
08
What a visitor finds when they're deciding whether to get in touch.
In short
Web Services gives a visitor more than any competitor page: prices, a form, a phone number and plain-English copy (reading ease 68). What it lacks is proof near the top. One client quote, halfway down, against a competitor showing 65 Google reviews in its first screen. And on a phone, the first screen has no button to get in touch.
| Site | Contact in first phone screen | Tap to call | Form | Prices | Reviews | Reading ease | Words |
|---|---|---|---|---|---|---|---|
| rgleeson.com | ✕ No | ✓ Yes | ✓ Form | £400, £150 | ✕ Quotes only | 68 | 958 |
| Competitor A | ✓ Contact Us | ✕ No | ✕ No | ✕ None | ✕ Quotes only | 57 | 576 |
| Competitor B | ✓ Let’s Talk | ✓ Yes | ✓ Form | ✕ None | ✕ Quotes only | 15 | 1,078 |
| Competitor C | ✓ Talk to us → | ✓ Yes | ✕ No | £2k, £6k | ✓ Rating | 64 | 852 |
| Competitor D | ✕ No | ✓ Yes | ✕ No | ✕ None | ✕ Quotes only | 49 | 588 |
09
The signals that tell browsers, search engines and visitors that the site is safe and the business is real.
In short
Sound. HTTPS everywhere with HSTS, the main security headers present, Lighthouse best practices 100, and the business described in structured data with its address and prices. The one gap is a Content Security Policy (F11), which only Competitor A sends.
| Site | HSTS | CSP | nosniff | Frame protection | Business in structured data | Best practices |
|---|---|---|---|---|---|---|
| rgleeson.com | ✓ Yes | ✕ No | ✓ Yes | ✓ Yes | ✓ ProfessionalService | 100 |
| Competitor A | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | ✓ LocalBusiness | 96 |
| Competitor B | ✕ No | ✓ Yes | ✕ No | ✕ No | ✕ No | 71 |
| Competitor C | ✓ Yes | ✕ No | ✕ No | ✕ No | ✓ Organization | 96 |
| Competitor D | ✕ No | ✕ No | ✕ No | ✕ No | ✓ ProfessionalService | 96 |
10
Three questions per finding: does it stop someone doing what they came for, does it affect many visitors or searches, and will it keep happening until it's fixed? Three yeses = Critical, two = Serious, one = Medium.
Stops a task: yesMany affected: yesKeeps happening: yes
People looking for a local web designer search for it, and AI assistants build their answers from the same results. A page that isn't in the top 20 isn't seen, however good it is.
Check Search Console for the impressions Web Services gets for Dover searches, so you start from real numbers. Then: ask your website clients for Google reviews; publish the Action Carpets and Downtogroundworks case studies with their towns named; list the business on the local directories that appear in these results (FreeIndex, Kent Small Business, Business Magnet); and link to Web Services from the home page's first screen.
Effort: Two to four hours to start; reviews and links build over months
Stops a task: yesMany affected: yesKeeps happening: yes
Google and AI assistants match a business across sources by its name. Here the listing's name points at someone else's website, and your website never claims it.
Pick one public name. If it stays RG Web Design, show "Trading as RG Web Design" on every page, add it as alternateName in the structured data and add the Google profile to sameAs. If the clash is a problem, rename the listing to match the site.
Effort: An hour, plus the naming decision
Stops a task: noMany affected: yesKeeps happening: yes
On desktop the same pages score 93 to 99, so this is a phone problem, and most local searches happen on phones. Speed is also one of the signals Google uses to rank pages.
Self-host the four font files and preload the two used above the fold; show the first screen without the reveal animation; load Analytics after the page has painted, or switch to a lighter tool. Re-run Lighthouse to confirm under 2.5s.
Effort: Half a day
Stops a task: noMany affected: yesKeeps happening: yes
Someone choosing between five web designers looks for proof that other local businesses chose you. Reviews are also one of the things that decides who appears in Google's map results.
Ask the clients on the Work page for a Google review. Once there are five or more, show the rating and count under the Web Services headline and add AggregateRating to the business's structured data.
Effort: An hour to ask; showing it takes twenty minutes
Stops a task: yesMany affected: noKeeps happening: yes
An agent acting for someone will read a contact form but won't fill in a stranger's form unprompted. A booking page with real slots is an action it can take. Few people use agents this way yet, which is why this isn't Critical.
Turn on bookings in the Google Business Profile, or publish a booking page, and link it from Web Services, Contact and the structured data.
Effort: An hour, plus deciding on available slots
Stops a task: noMany affected: yesKeeps happening: yes
Google trims long titles and descriptions in results, often mid-sentence, and assistants that quote them do the same.
Rewrite the 15 descriptions to under 155 characters with the answer first, and shorten the 7 post title tags.
Effort: Two hours
Stops a task: noMany affected: noKeeps happening: yes
The case studies are the evidence behind the services. Without structured data, nothing tells an assistant that each one is work by the same person and business.
Add ProfilePage to About, ContactPage to Contact, and a CreativeWork to each case study, all pointing to the existing #richard and #business entities.
Effort: Half a day
Stops a task: noMany affected: noKeeps happening: yes
Every extra kilobyte is a wait on a phone signal, and a lazy-loaded image in the first screen is fetched late on purpose.
Serve 800, 1,200 and 2,000px versions with srcset and sizes, and drop loading="lazy" from any image in the first screen.
Effort: Two hours, scripted
Stops a task: noMany affected: noKeeps happening: yes
Screen readers and agents use the heading outline to understand a page. A skipped level suggests a missing section.
Make the footer headings h2, styled as they are now, or plain labels.
Effort: Fifteen minutes
Stops a task: noMany affected: noKeeps happening: yes
Small targets are hard to tap, and an agent working from a screenshot may not register them as controls.
Add vertical padding so the links are at least 24px tall.
Effort: Ten minutes
Stops a task: noMany affected: noKeeps happening: yes
A policy stops injected scripts running if anything on the page is ever compromised, such as a third-party script.
Add a CSP in the hosting config that allows this site, the two font services and Google Analytics, in report-only mode for a week first.
Effort: An hour
Stops a task: noMany affected: noKeeps happening: yes
Each hop adds a round trip and a chance for a crawler to give up.
Point the http apex straight at https://www in the hosting settings.
Effort: Ten minutes
11
Every finding and recommendation, in the order I'd do them. Most of the first week is under an hour each.
| Item | What to do | Effort | Severity |
|---|---|---|---|
| F1 | You're not in the top 20 for "web design Dover" Check Search Console for the impressions Web Services gets for Dover searches, so you start from real numbers. Then: ask your website clients for Google reviews; publish the Action Carpets and Downtogroundworks case studies with their towns named; list the business on the local directories that appear in these results (FreeIndex, Kent Small Business, Business Magnet); and link to Web Services from the home page's first screen. | Two to four hours to start; reviews and links build over months | Critical |
| F2 | Your Google listing's name is missing from your site, and another business owns it Pick one public name. If it stays RG Web Design, show "Trading as RG Web Design" on every page, add it as alternateName in the structured data and add the Google profile to sameAs. | An hour, plus the naming decision | Critical |
| F6 | Search snippets get cut short Rewrite the 15 descriptions to under 155 characters with the answer first, and shorten the 7 post title tags. | Two hours | Serious |
| F9 | Footer headings skip a level on every page Make the footer headings h2, styled as they are now, or plain labels. | Fifteen minutes | Medium |
| F10 | Six links are under the 24px tap target Add vertical padding so the links are at least 24px tall. | Ten minutes | Medium |
| F12 | One address takes two redirects Point the http apex straight at https://www in the hosting settings. | Ten minutes | Medium |
| Item | What to do | Effort | Severity |
|---|---|---|---|
| F3 | Pages take 3.5 to 5.4 seconds to show their main content on a phone Self-host the four font files and preload the two used above the fold; show the first screen without the reveal animation; load Analytics after the page has painted, or switch to a lighter tool. Re-run Lighthouse to confirm under 2.5s. | Half a day | Serious |
| F4 | There's no rating or review count anywhere on Web Services Ask the clients on the Work page for a Google review. Once there are five or more, show the rating and count under the Web Services headline and add AggregateRating to the business's structured data. | An hour to ask; showing it takes twenty minutes | Serious |
| F5 | An AI agent can't book a call with you Turn on bookings in the Google Business Profile, or publish a booking page, and link it from Web Services, Contact and the structured data. | An hour, plus deciding on available slots | Serious |
| F7 | Half the pages carry no structured data Add ProfilePage to About, ContactPage to Contact, and a CreativeWork to each case study, all pointing to the existing #richard and #business entities. | Half a day | Medium |
| F8 | Images are heavier than they need to be Serve 800, 1,200 and 2,000px versions with srcset and sizes, and drop loading="lazy" from any image in the first screen. | Two hours, scripted | Medium |
| F11 | No Content Security Policy Add a CSP in the hosting config that allows this site, the two font services and Google Analytics, in report-only mode for a week first. | An hour | Medium |
| Item | What to do | Effort |
|---|---|---|
| R1 | Most of the text is grey, not ink Keep grey for supporting text, but set the opening paragraph and card descriptions in ink. Contrast between levels is what makes the hierarchy, and right now most text sits on the second level. | An hour |
| R2 | 14 type sizes on one page Fold the stray sizes into the nearest step of a 9-step scale (13, 15, 16, 20, 24, 32, 44, 64, 80) and name each as a token, so new pages can't add more. | Two hours |
| R3 | No proof in the first screen Add one line of proof under the headline: a client result ("Vancat: sales up 200%") or, once there are enough, the Google rating and review count. | An hour |
| R4 | Content waits for an animation Show the first screen without any reveal, and keep the fade for content further down. This is part of finding F3. | Part of F3 |
Re-run the same scripts a month after the fixes and compare. The scores, positions and speed figures in this report are the baseline.
12
Every number in this report comes from a script or a dated test, and every score comes from the rules below, applied the same way to all five sites. Lighthouse 12.2.1; Chrome at 375 and 1440px; measured 4 November 2026.
| Measurement | Tool | Scope |
|---|---|---|
| Raw vs rendered words, crawler fetches, robots, llms.txt, landmarks, names, labels, tap targets, focus | scripts/ai-readiness-audit.mjs | All 32 sitemap pages, 2 widths, 5 crawlers |
| Colour, type, contrast, calls to action, reviews, prices, reading ease, headers | scripts/site-audit.mjs | Web Services, home, and each competitor's ranking page |
| Speed, Lighthouse scores, page weight | Lighthouse via scripts/lighthouse-summary.mjs | 20 runs: 6 pages here and 4 competitors, phone and desktop |
| Links and images | scripts/link-check.mjs | 32 internal and 18 external links, 152 images |
| Search positions | Firecrawl search, located in Dover | 5 searches, top 10 to 20 results |
| Design review | By eye, against the rubric in section 7 | First screen and full scroll, 2 widths |
| Check | 16 September | 4 November 2026 |
|---|---|---|
| Content readable without JavaScript | Homepage only checked: 731 words | All 32 pages pass |
| Prices in structured data | None | Web design from £400; audit £150 |
| FAQ markup | None | FAQPage on the FAQ page |
| Name matches the Google listing | No | Still no (F2) |
| Agent-bookable scheduling | None | Still none (F5) |
| Interface checked for agents | Not tested | 32 pages at two widths: 6 small targets |
Category scores are out of 100. The overall score is the weighted average. Grades: A 85+, B 70+, C 55+, D 40+.
| Rule | Points | rgleeson.com |
|---|---|---|
| Words in the raw HTML: 300 or more, and at least 90% of what a visitor sees | 25 | 25 |
| An AI crawler (GPTBot) is sent the same page as a browser | 25 | 25 |
| robots.txt lets the AI crawlers in | 10 | 10 |
| An llms.txt file | 5 | 5 |
| Structured data that parses | 15 | 15 |
| One main landmark | 5 | 5 |
| A skip link | 5 | 5 |
| Every control 24px or more on a phone | 10 | 10 |
| Rule | Points | rgleeson.com |
|---|---|---|
| Lighthouse SEO score (mobile) × 0.3 | 30 | 30 |
| Title 30 to 60 characters | 10 | 10 |
| Description 70 to 160 characters | 10 | 0 |
| Canonical link | 5 | 5 |
| Open Graph title, description, image and URL | 5 | 5 |
| One h1 | 5 | 5 |
| No skipped heading levels | 5 | 0 |
| A sitemap, declared in robots.txt | 10 | 10 |
| Position for "web design Dover": top 3 = 20, top 10 = 12, top 20 = 5 | 20 | 0 |
| Rule | Points | rgleeson.com |
|---|---|---|
| Lighthouse performance, mobile × 0.5 | 50 | 41 |
| Lighthouse performance, desktop × 0.2 | 20 | 20 |
| Main content painted on a phone: 2.5s or less = 15, 4s or less = 7 | 15 | 0 |
| Page weight on a phone: under 1 MB = 15, under 2 MB = 7 | 15 | 15 |
| Rule | Points | rgleeson.com |
|---|---|---|
| Lighthouse accessibility score (mobile) × 0.5 | 50 | 49 |
| Text failing contrast: 1% or less = 20, 5% or less = 10 | 20 | 20 |
| Every control 24px or more on a phone | 10 | 10 |
| Every image has alt text (empty is fine for decoration) | 10 | 10 |
| Header, navigation, main and footer landmarks, plus a skip link | 10 | 10 |
| Rule | Points | rgleeson.com |
|---|---|---|
| Expert review: hierarchy, consistency, imagery, distinctiveness (0 to 20) × 2.5 | 50 | 38 |
| Two typefaces or fewer (three = 5) | 10 | 5 |
| Type sizes in use: 10 or fewer = 10, 14 or fewer = 5 | 10 | 5 |
| Body text 16px or more, line height 1.4 to 1.8 | 10 | 10 |
| Line length 45 to 85 characters at desktop | 10 | 10 |
| Layout shift 0.1 or less on phone and desktop | 10 | 10 |
| Rule | Points | rgleeson.com |
|---|---|---|
| A way to get in touch in the first screen on a phone | 15 | 0 |
| A way to get in touch in the first screen on desktop | 10 | 10 |
| A tap-to-call phone link | 10 | 10 |
| An email link | 5 | 5 |
| An enquiry form on the page | 10 | 10 |
| Prices shown | 15 | 15 |
| Reviews or a client testimonial on the page | 10 | 10 |
| Reading ease (Flesch) 60 or more = 10, 50 or more = 5 | 10 | 10 |
| Words on the page: 600 or more = 15, 300 or more = 7 | 15 | 15 |
| Rule | Points | rgleeson.com |
|---|---|---|
| HSTS header | 10 | 10 |
| nosniff, referrer policy and frame protection headers | 15 | 15 |
| Content Security Policy | 5 | 0 |
| Business named in structured data | 20 | 20 |
| Rating in structured data (AggregateRating) | 15 | 0 |
| Lighthouse best practices (mobile) × 0.2 | 20 | 20 |
| A tap-to-call phone link | 15 | 15 |
The same measurements, the same benchmark against your local competitors (named, in your copy), the same report. £150, credited in full if you go on to a build. Email richardgleeson83@gmail.com or ring +44 7823 77 88 95.