Website review, no card needed

counterline.co.uk logo

counterline.co.uk website review

Visit site (opens in a new tab)Reviewed 20 October 202623 issues · 81 checks

This review found 23 issues worth fixing on counterline.co.uk, 4 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.5 s1.7 sMay 2Oct 172.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20262.0 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.4 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.2 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.4 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
114 ms91 msMay 2Oct 1796 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202698 ms
May 23, 2026106 ms
May 30, 2026105 ms
Jun 6, 2026111 ms
Jun 13, 2026104 ms
Jun 20, 2026105 ms
Jun 27, 202696 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 2026102 ms
Aug 15, 2026103 ms
Aug 22, 2026103 ms
Aug 29, 2026103 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202694 ms
Sep 26, 202694 ms
Oct 3, 202697 ms
Oct 17, 202696 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 counterline.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. counterline.co.uk at 0.4 s0.4 s
  2. counterline.co.uk at 0.9 s0.9 s
  3. counterline.co.uk at 1.3 s1.3 s
  4. counterline.co.uk at 1.8 s1.8 s
  5. counterline.co.uk at 2.2 s2.2 s
  6. counterline.co.uk at 2.7 s2.7 s
  7. counterline.co.uk at 3.1 s3.1 s
  8. counterline.co.uk at 3.6 s3.6 s

Speed

2 to fix84
  • Mobile performance score: 84

    84/100

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

  • Font display

    350 ms

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

  • Improve image delivery

    250 ms · 33 KiB

    2 images could be 33 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.

  • Reduce unused CSS

    150 ms · 47 KiB

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

  • Render-blocking requests

    150 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.

  • 3 third-party services on the page

    3 third-party services load with your homepage (wpmucdn.com, Google Fonts and assetcdn.net), adding 236 KiB and 24 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 41 ms of it running JavaScript. That is comfortably low.

  • Server response: 123 ms

    123 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

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

    +51%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “integrale food counters”.

  • Speed Index: 3.7 s

    3.7 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

5 checks passed
  • 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.01

    0.01

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

  • Time to Interactive: 3.5 s

    3.5 s

    The page is fully interactive after 3.5 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.10 g of CO₂ per visit

    0.10 g

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

4 checks passed
  • Page weight: 356 KiB in 20 requests

    356 KiB

    Your homepage downloads 356 KiB in 20 requests on a phone: fonts 177 KiB (4), stylesheets 73 KiB (9) and images 70 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8291
  • 10 text elements with low contrast

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

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

    All page content should be contained by landmarks: 36 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 (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h6, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10093
  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 161 internal links, 11 external

    The homepage links to 161 pages on counterline.co.uk and 11 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “The UK’s leading manufacturer of food and drink display units and bespoke counters for the catering, hospitality & food…”.

  • One H1 headline

    Your main headline reads: “Exporting throughout the world”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Retail and Catering Product Display Suppliers | Counterline”.

  • Canonical URL set

    The canonical URL is https://counterline.co.uk/.

  • Structured data in place

    Structured data found: Organization, Person and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://counterline.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.

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.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 2 pages share a title

    https://counterline.co.uk/idesign/vision-aire/vision-aire-specification-sheets and https://counterline.co.uk/idesign/manhattan/manhattan-specification-sheets all use the title “Industrial Catering Equipment Brochure Downloads | Counterline”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://counterline.co.uk/idesign/vision-aire/vision-aire-specification-sheets and https://counterline.co.uk/idesign/manhattan/manhattan-specification-sheets use the same meta description. A description written for each page earns more clicks.

  • 15 pages slow to respond

    https://counterline.co.uk/idesign, https://counterline.co.uk/idesign/vision-aire, https://counterline.co.uk/idesign/vision-aire/hot-holding-display-cabinet, https://counterline.co.uk/idesign/vision-aire/vision-aire-chilled, https://counterline.co.uk/idesign/vision-aire/patisserie-display-counter and https://counterline.co.uk/idesign/vision-aire/vision-aire-specification-sheets and 9 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 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 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    7 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • No opening hours

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

  • 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 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 599 words of copy

    The homepage carries about 599 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Case Study: JG Ross Coffee Shop & Bakery”, “Contact” and “Brochure Download”.

  • 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: 6 testimonial or review blocks and 12 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Matomo.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

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

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 counterline.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2017.

Stack

CMS
WordPress
Analytics
Google Analytics | Google Tag Manager | Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on counterline.co.uk, including 11 speed issues, 2 SEO issues and 2 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