Website review, no card needed
names.co.uk website review
Visit site (opens in a new tab)Reviewed 24 October 202626 issues · 79 checks
This review found 26 issues worth fixing on names.co.uk, 10 of them high impact, across 79 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
Site score
79CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 150 ms |
| May 9, 2026 | 152 ms |
| May 16, 2026 | 156 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 169 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 167 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 151 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 157 ms |
| Oct 17, 2026 | 158 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Reduce unused JavaScript
1.8 s · 299 KiBAbout 299 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.1 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 47
47/100Your mobile performance score is 47 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
450 ms · 579 KiB29 files are served with short cache lifetimes, so returning visitors download them again (579 KiB).
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, iubenda and isy-teamblue.services and others), adding 663 KiB and 518 ms of main-thread time.
Google Tag Manager adds 422 ms
422 msGoogle Tag Manager costs a phone 422 ms of main-thread work and 536 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 763 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
250 ms · 146 KiB4 images could be 146 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 215 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Document request latency
32 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
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: 204 ms
204 msYour server sent the HTML in 204 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: 11.2 s
11.2 sYour largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We (Team Blue Internet Services UK Limited t/a names.co.uk)…”.
Time to Interactive: 11.4 s
11.4 sThe page becomes fully interactive after 11.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.355
0.355The layout shifts by 0.355 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 150 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 177 ms
177 msReal visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 185 ms
185 msScripts block the page for only 185 ms while loading. Good is under 200 ms.
Images and page weight
2 images far larger than shown
54 KiB2 images are downloaded at several times the size a phone draws them, for example kevin-hall-f60484331066.webp at 970 px wide, shown at 264 px. Resized copies would save about 54 KiB.
4 images below the first screen load straight away
4 images further down the page (226 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.5 MB in 95 requests
1.5 MBYour homepage downloads 1.5 MB in 95 requests on a phone: scripts 852 KiB (24), images 527 KiB (54) and fonts 72 KiB (5). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
86 internal links, 19 external
The homepage links to 86 pages on names.co.uk and 19 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Register your domain, build your website and get reliable UK hosting. Claim a FREE .co.uk domain for your first year. E…”.
One H1 headline
Your main headline reads: “Search for your perfect domain name”.
Title: 64 characters
Your title is a healthy 64 characters: “Domain Names, Hosting & Email | FREE .co.uk Domain | names.co.uk”.
Canonical URL set
The canonical URL is https://www.names.co.uk/.
Structured data in place
Structured data found: WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.names.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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,603 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.names.co.uk/llms.txt (5 KiB, 26 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.names.co.uk/support/articles/how-to-setup-email-on-your-device has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages slow to respond
https://www.names.co.uk/domain-names/info/domain-transfers, https://www.names.co.uk/domain-names/extensions/com, https://www.names.co.uk/domain-names/online-brand-protection/domain-acquisition and https://www.names.co.uk/domain-names/online-brand-protection/managed-dns-solutions took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 57 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://trk.names.co.uk/messages/he-man_messages?tke=JTdCJTIyaGFzaCUyMiUzQSUyMjE3OTI4NTA1OTg5OTdfOHZvODJkemg1M3dfOWM5Z3RvJTIyJTJDJTIyZG9tYWluJTIyJTNBJTIybmFtZXMuY28udWslMjIlMkMlMjJmaWVsZCUyMiUzQSUyMm1.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
2 checks passed
Tap targets are thumb-sized
15 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 868 words of copy
The homepage carries about 868 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Try our free plan” and “Learn more and customise”.
12 calls to action
The homepage has 12 calls to action, for example “Contact Us”, “Buy a domain name” and “Buy .com domain”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks, 1 customer or partner logo and 13 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
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 names.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Founded
- 1996
- Headquarters
- Worcester
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on names.co.uk, including 17 speed issues and 1 SEO issue. 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.