Website review, no card needed

arco.co.uk logo

arco.co.uk website review

Visit site (opens in a new tab)Reviewed 26 October 202660 issues · 106 checks

This review found 60 issues worth fixing on arco.co.uk, 21 of them high impact, across 106 checks. The most urgent: render-blocking requests. 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.5 s2.1 sMay 9Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
223 ms207 msMay 9Oct 17212 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026209 ms
May 16, 2026212 ms
May 23, 2026212 ms
May 30, 2026213 ms
Jun 6, 2026215 ms
Jun 20, 2026219 ms
Jun 27, 2026219 ms
Jul 4, 2026220 ms
Jul 11, 2026221 ms
Jul 25, 2026219 ms
Aug 1, 2026219 ms
Aug 8, 2026220 ms
Aug 15, 2026220 ms
Aug 22, 2026221 ms
Aug 29, 2026220 ms
Sep 5, 2026216 ms
Sep 12, 2026213 ms
Sep 19, 2026212 ms
Sep 26, 2026212 ms
Oct 3, 2026212 ms
Oct 10, 2026212 ms
Oct 17, 2026212 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 arco.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. arco.co.uk at 0.6 s0.6 s
  2. arco.co.uk at 1.2 s1.2 s
  3. arco.co.uk at 1.8 s1.8 s
  4. arco.co.uk at 2.4 s2.4 s
  5. arco.co.uk at 3.0 s3.0 s
  6. arco.co.uk at 3.6 s3.6 s
  7. arco.co.uk at 4.2 s4.2 s
  8. arco.co.uk at 4.8 s4.8 s

Speed

14 to fix39
  • Render-blocking requests

    3.5 s

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

  • Use efficient cache lifetimes

    1.9 s · 1.5 MB

    59 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • Document request latency

    1.4 s

    The HTML itself could arrive about 1.4 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.3 s

    Reduce initial server response time. Google estimates savings of 1.3 s on a phone.

  • Reduce unused CSS

    1.1 s · 232 KiB

    About 232 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 39

    39/100

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

  • Improve image delivery

    950 ms · 404 KiB

    9 images could be 404 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, incontact.eu and Optanon and others), adding 1.4 MB and 680 ms of main-thread time.

  • Google Tag Manager adds 388 ms

    388 ms

    Google Tag Manager costs a phone 388 ms of main-thread work and 758 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.6 s

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

  • incontact.eu adds 173 ms

    173 ms

    incontact.eu costs a phone 173 ms of main-thread work and 299 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.

  • 2,005 HTML elements

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

  • Server response: 1.4 s

    1.4 s

    Your server takes 1.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

Core Web Vitals

10 to fix33
  • 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.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Arco Professional Safety Services We go beyond PPE, offerin…”.

  • Time to Interactive: 24.8 s

    24.8 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Real-user INP: 209 ms

    209 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • 47 images without width and height

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

  • Cumulative Layout Shift: 0.226

    0.226

    The layout shifts by 0.226 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 354 ms

    354 ms

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

  • Tap response (INP) held steady for real visitors

    +1%

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

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

    +10%

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

3 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 546 ms

    546 ms

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

Images and page weight

4 to fix43
  • Page weight: 4.5 MB in 145 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 145 requests on a phone: images 2.0 MB (62), scripts 2.0 MB (42) and stylesheets 259 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (1.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 12 images below the first screen load straight away

    12 images further down the page (730 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images far larger than shown

    258 KiB

    6 images are downloaded at several times the size a phone draws them, for example logo-trojan.svg at 300 px wide, shown at 81 px. Resized copies would save about 258 KiB.

  • About 1.3 g of CO₂ per visit

    1.27 g

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

Accessibility

13 to fixGoogle 7484
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 5 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

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

    All page content should be contained by landmarks: 2 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.

  • 8 form fields without a label

    8 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 (15 elements)

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

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 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 (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8582
  • Title is long (153 characters)

    Your title is 153 characters, so Google will cut it off around 60: “Arco | Experts in Safety and the UK and Ireland's leading supplier of safety equipment, w…”.

  • Structured data has 3 problems

    Structured data found (Organization and WebSite) but with 3 problems, for example “WebSite: missing name”.

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

  • 13 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 170 internal links, 11 external

    The homepage links to 170 pages on arco.co.uk and 11 external pages.

5 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Arco, Experts in Safety and the UK and Ireland's leading supplier of safety equipment, workwear, safety boots and shoes…”.

  • One H1 headline

    Your main headline reads: “TROJAN offers now on. Save up to 50%*”.

  • Canonical URL set

    The canonical URL is https://www.arco.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://www.arco.co.uk/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description 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://www.arco.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 (5,642 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix50
  • 1 page without a title

    https://www.arco.co.uk/Web-Taxonomy/Workplace-Safety/c/WEB_3229492 has no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    /;jsessionid=A4C6CDB47A541AD9338D1AF2F628098F declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 linked page hidden from search

    https://www.arco.co.uk/Web-Taxonomy/Workplace-Safety/c/WEB_3229492 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and /;jsessionid=A4C6CDB47A541AD9338D1AF2F628098F all use the title “Arco | Experts in Safety and the UK and Ireland's leading supplier of…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.arco.co.uk/help, https://www.arco.co.uk/store-finder;jsessionid=A4C6CDB47A541AD9338D1AF2F628098F, https://www.arco.co.uk/login;jsessionid=A4C6CDB47A541AD9338D1AF2F628098F, https://www.arco.co.uk/mfaLogin/redirectForgottenPassword;jsessionid=A4C6CDB47A541AD9338D1AF2F628098F, https://www.arco.co.uk/Web-Taxonomy/First-Aid/c/WEB_3229496 and https://www.arco.co.uk/Web-Taxonomy/Workplace-Safety/c/WEB_3229492 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.arco.co.uk/Web-Taxonomy/Workplace-Safety/c/WEB_3229492 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.arco.co.uk/mfaLogin/redirectForgottenPassword;jsessionid=A4C6CDB47A541AD9338D1AF2F628098F 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.

  • 4 pages slow to respond

    https://www.arco.co.uk/Web-Taxonomy/Personal-Protective-Equipment/c/WEB_329238, https://www.arco.co.uk/Web-Taxonomy/Clothing/c/WEB_5, https://www.arco.co.uk/Web-Taxonomy/Gloves/c/WEB_329234 and https://www.arco.co.uk/Web-Taxonomy/Cleaning-and-Hygiene/c/WEB_329236 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

3 to fixGoogle 5480
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=3d9f569f-085f-409d-8f5b-358b013f6925&referrer=&landingpage=https%3A%2F%2Fwww.arco.co.uk%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017.

  • Deprecated browser APIs

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • 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

    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

4 to fix75
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 926 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact Us”, “Quick Order” and “My Account Register | Sign In”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

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

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 arco.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
Hosting
Imperva

Hiring

Hiring
414 open roles
Teams
Project Management (147), Superintendent (104), Interns/Co-ops (57), Business Development (15)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 60 issues on arco.co.uk, including 24 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

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