firstchoice-cs.co.uk website review

39 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.

About 337 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

17 files are served with short cache lifetimes, so returning visitors download them again (296 KiB).

240 KiB could be saved by minifying JavaScript.

Your mobile performance score is 37 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 6,474 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

A phone's processor spends 6.4 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

19 long tasks block the main thread while loading, the longest for 682 ms. During a long task the page ignores taps.

8 third-party services load with your homepage (Usercentrics CMP, freshworks.com and Feefo.com and others), adding 1.0 MB and 461 ms of main-thread time.

23 KiB could be saved by minifying CSS.

21 images could be 280 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Feefo.com costs a phone 95 ms of main-thread work and 297 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.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site is provided to you by Parts Town UK Limited. We u…”.

The page becomes fully interactive after 21.7 s. Good is under 3.8 s.

Visually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 915 ms in total while the page loads. Good is under 200 ms.

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

52 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 126 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 391 requests on a phone: scripts 1.5 MB (257), images 1.2 MB (62) and fonts 498 KiB (15). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 images have no alt text, which hurts accessibility and image search.

3 dropdowns have no label.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

Elements with role="none" or role="presentation" have conflicts (2 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.partstown.co.uk/sitemap.xml, so Google discovers your pages only by following links.

12 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 1,025 pages on firstchoice-cs.co.uk and 32 external pages.

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.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/manufacturers/3m, /manufacturers/adande-refrigeration, /manufacturers/ambach, /manufacturers/b-pro, /manufacturers/blodgett and /manufacturers/comenda and 7 others all use the title “Client Challenge”. Search engines can't tell which page to show for a search, so each competes with the others.

/manufacturers, /manufacturers/3m, /manufacturers/adande-refrigeration, /manufacturers/ambach, /manufacturers/b-pro and /manufacturers/blodgett and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/manufacturers/3m, /manufacturers/adande-refrigeration, /manufacturers/ambach, /manufacturers/b-pro, /manufacturers/blodgett and /manufacturers/comenda and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/manufacturers/3m, /manufacturers/adande-refrigeration, /manufacturers/ambach, /manufacturers/b-pro, /manufacturers/blodgett and /manufacturers/comenda and 7 others have 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.

We fetched 15 pages linked from your homepage (of 200 found) and read each the way a search engine does.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

Chrome logged issues while loading the page (“Content security policy”).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block, 1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

partstown.co.uk has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

partstown.co.uk's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

The homepage has only about 13 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be firstchoice-cs.co.uk is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.