Website review, no card needed

seat.co.uk logo

seat.co.uk website review

Visit site (opens in a new tab)Reviewed 19 October 202638 issues · 85 checks

This review found 38 issues worth fixing on seat.co.uk, 10 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s2.1 sApr 25Oct 102.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.2 s
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
168 ms134 msApr 25Oct 10160 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026138 ms
May 2, 2026140 ms
May 9, 2026141 ms
May 16, 2026142 ms
May 23, 2026141 ms
May 30, 2026142 ms
Jun 6, 2026146 ms
Jun 13, 2026148 ms
Jun 20, 2026150 ms
Jun 27, 2026150 ms
Jul 4, 2026150 ms
Jul 11, 2026150 ms
Jul 18, 2026152 ms
Jul 25, 2026152 ms
Aug 1, 2026153 ms
Aug 8, 2026154 ms
Aug 15, 2026156 ms
Aug 22, 2026161 ms
Aug 29, 2026163 ms
Sep 5, 2026164 ms
Sep 12, 2026162 ms
Sep 19, 2026162 ms
Sep 26, 2026161 ms
Oct 3, 2026159 ms
Oct 10, 2026160 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

Full-page screenshot of seat.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. seat.co.uk at 0.5 s0.5 s
  2. seat.co.uk at 0.9 s0.9 s
  3. seat.co.uk at 1.4 s1.4 s
  4. seat.co.uk at 1.9 s1.9 s
  5. seat.co.uk at 2.3 s2.3 s
  6. seat.co.uk at 2.8 s2.8 s
  7. seat.co.uk at 3.3 s3.3 s
  8. seat.co.uk at 3.7 s3.7 s

Speed

11 to fix60
  • Reduce unused JavaScript

    2.9 s · 538 KiB

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

  • Render-blocking requests

    2.1 s

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

  • Use efficient cache lifetimes

    1.1 s · 321 KiB

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

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60 (desktop: 78). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and Optanon and others), adding 1.1 MB and 748 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 187 KiB

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

  • Google Tag Manager adds 378 ms

    378 ms

    Google Tag Manager costs a phone 378 ms of main-thread work and 566 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.

  • Font display

    300 ms

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

  • Improve image delivery

    273 KiB

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

  • Main-thread work: 2.7 s

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

  • 1,594 HTML elements

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • 9 long tasks on the main thread

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

  • 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 16.6 s

    16.6 s

    Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A close-up frontal shot of a new green SEAT Arona”.

  • Time to Interactive: 18.9 s

    18.9 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 29 images without width and height

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

  • Total Blocking Time: 227 ms

    227 ms

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

  • Largest content (LCP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 676 ms

    676 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.8 MB in 164 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 164 requests on a phone: scripts 1.3 MB (53), fonts 615 KiB (6) and images 563 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    seat-new-ibiza-pa-liminal-612x278.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.8 g of CO₂ per visit

    0.79 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.9 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

7 to fixGoogle 8691
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 6 text elements with low contrast

    6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (103 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (8 elements).

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 47 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: 47 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9290
  • 2 H1 headlines

    There are 2 <h1> headlines (“The New SEAT Arona” and “The New SEAT Ibiza”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 143 internal links, 11 external

    The homepage links to 143 pages on seat.co.uk and 11 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Welcome to the world of SEAT. You're in the right place to discover your new dream car with our extensive range. Explor…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Discover our range of new & used cars | SEAT UK”.

  • Canonical URL set

    The canonical URL is https://www.seat.co.uk/.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.seat.co.uk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.seat.co.uk/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.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,219 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 3 pages share a title

    https://www.seat.co.uk/configurator/w/model, https://www.seat.co.uk/configurator/w/version and https://www.seat.co.uk/configurator.html/version all use the title “Build your perfect SEAT with our car configurator | SEAT UK”. 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://www.seat.co.uk/configurator/w/model, https://www.seat.co.uk/configurator/w/version and https://www.seat.co.uk/configurator.html/version use the same meta description. A description written for each page earns more clicks.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.seat.co.uk/configurator/w/model, whose canonical is https://www.seat.co.uk/configurator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.seat.co.uk/car-dealers-locator, https://www.seat.co.uk/configurator/w/model, https://www.seat.co.uk/car-shopping-tools/test-drive, https://www.seat.co.uk/new-cars/new-car-stock-locator, https://www.seat.co.uk/configurator/w/version and https://www.seat.co.uk/configurator.html/version and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 53 small tap targets

    53 of 96 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “_satellite is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,077 words of copy

    The homepage carries about 1,077 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a Service Online” and “Buy a Service Plan”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Book a Test Drive”, “Learn more” and “Request yours now”.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 seat.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Employees
14,752
Founded
1950
Headquarters
Q15623

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on seat.co.uk, including 17 speed issues, 3 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25