Website review, no card needed
dwaligners.co.uk website review
Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 86 checks
This review found 42 issues worth fixing on dwaligners.co.uk, 18 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.7 s
4.0 s
5.3 s
6.6 s
8.0 s
9.3 s
10.6 s
Speed
Reduce unused JavaScript
6.4 s · 2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.
smile2impress.com adds 4.2 s
4.2 ssmile2impress.com costs a phone 4.2 s of main-thread work and 3.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Avoid multiple page redirects
2.3 sThe page goes through 2 redirects before it starts loading, costing about 2.3 s. Link and advertise the final URL directly.
Main-thread work: 11.8 s
A phone's processor spends 11.8 s on main-thread work while loading, 6.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (smile2impress.com, Google Tag Manager and Google CDN and others), adding 5.4 MB and 5.4 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
Google Tag Manager adds 551 ms
551 msGoogle Tag Manager costs a phone 551 ms of main-thread work and 870 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google CDN adds 338 ms
338 msGoogle CDN costs a phone 338 ms of main-thread work and 736 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
1,679 HTML elements
The page has 1,679 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
50 msThe HTML itself could arrive about 50 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 306 ms
306 msYour server sent the HTML in 306 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 20.5 s
20.5 sYour largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 5.5 s
5.5 sScripts block taps and scrolling for 5.5 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 34.8 s
34.8 sThe page becomes fully interactive after 34.8 s. Good is under 3.8 s.
Speed Index: 14.0 s
14.0 sVisually, the page fills in at 14.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user INP: 279 ms
279 msReal visitors wait 279 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
5 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 420 ms
420 msReal visitors wait 420 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 146 requests
6.7 MBYour homepage downloads 6.7 MB in 146 requests on a phone: scripts 4.3 MB (55), other files 976 KiB (47) and fonts 951 KiB (11). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (41 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.90 g of CO₂e: 228.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 buttons without a name
15 buttons have no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
41 images without alt text
41 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (74 elements)
All page content should be contained by landmarks: 74 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (6 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 6 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (95 characters)
Your title is 95 characters, so Google will cut it off around 60: “Diamond Whites Invisible Dental Aligners | Get Straight Teeth At Home – Diamond Whites Al…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (234 characters)
Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
28 internal links, 15 external
The homepage links to 28 pages on dwaligners.co.uk and 15 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Straight teeth,without the expense”.
Canonical URL set
The canonical URL is https://dwaligners.co.uk/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://dwaligners.co.uk/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
54%The HTML your server sends has 534 of the 983 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
llms.txt published
The site publishes https://dwaligners.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://dwaligners.co.uk/pages/privacy-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages share 2 titles
https://dwaligners.co.uk/pages/dr-richard and https://dwaligners.co.uk/pages/contact all use the title “Impress | Why choose clear aligners?”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://dwaligners.co.uk/pages/dr-richard and https://dwaligners.co.uk/pages/contact use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://dwaligners.co.uk/pages/faqs has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 8 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187277627&tm=gtm002&Ver=2&mid=3a679c6a-4475-4c2f-8e09-b04357d39c34&bo=1&sid=5666f790d8f111f1b2a2273384c3270b&vid=56673500d8f111f1856da33bf95cd770&vids=1&msclkid=N&pi=9.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 983 words of copy
The homepage carries about 983 words of visible text.
4 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Book a visit”, “Pricing” and “Contact”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Microsoft Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 4 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at dwaligners.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · hulkapps.com · fbot.me · b-cdn.net · rechargecdn.com · herokuapp.com · pop-convert.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Company
- Headquarters
- Hatfield
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on dwaligners.co.uk, including 17 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.