Website review, no card needed

briggsequipment.co.uk logo

briggsequipment.co.uk website review

Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 90 checks

This review found 31 issues worth fixing on briggsequipment.co.uk, 12 of them high impact, across 90 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.9 s1.4 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
113 ms93 msMay 9Oct 24111 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202696 ms
May 16, 202698 ms
May 23, 202698 ms
May 30, 2026104 ms
Jun 6, 2026109 ms
Jun 13, 2026106 ms
Jun 20, 2026111 ms
Jun 27, 2026104 ms
Jul 4, 202699 ms
Jul 11, 202697 ms
Jul 18, 202696 ms
Jul 25, 202695 ms
Aug 1, 202697 ms
Aug 8, 2026102 ms
Aug 15, 202697 ms
Aug 22, 2026105 ms
Aug 29, 2026105 ms
Sep 5, 2026103 ms
Sep 12, 2026105 ms
Sep 19, 2026102 ms
Sep 26, 2026102 ms
Oct 3, 2026105 ms
Oct 10, 2026107 ms
Oct 17, 2026107 ms
Oct 24, 2026111 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 briggsequipment.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. briggsequipment.co.uk at 0.7 s0.7 s
  2. briggsequipment.co.uk at 1.3 s1.3 s
  3. briggsequipment.co.uk at 2.0 s2.0 s
  4. briggsequipment.co.uk at 2.6 s2.6 s
  5. briggsequipment.co.uk at 3.3 s3.3 s
  6. briggsequipment.co.uk at 3.9 s3.9 s
  7. briggsequipment.co.uk at 4.6 s4.6 s
  8. briggsequipment.co.uk at 5.2 s5.2 s

Speed

12 to fix49
  • Render-blocking requests

    5.2 s

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

  • Reduce unused CSS

    1.4 s · 406 KiB

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

  • Mobile performance score: 49

    49/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, freshworks.com and customergauge.com and others), adding 1.4 MB and 805 ms of main-thread time.

  • Use efficient cache lifetimes

    903 KiB

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

  • Improve image delivery

    746 KiB

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

  • Reduce unused JavaScript

    150 ms · 439 KiB

    About 439 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google Tag Manager adds 333 ms

    333 ms

    Google Tag Manager costs a phone 333 ms of main-thread work and 338 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: 3.0 s

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

  • 9 long tasks on the main thread

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

  • 1,618 HTML elements

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

  • customergauge.com adds 91 ms

    91 ms

    customergauge.com costs a phone 91 ms of main-thread work and 584 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

    50 ms

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

  • Legacy JavaScript

    22 KiB

    Polyfills for old browsers add 22 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.

  • Forced reflow

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hyster XTLG”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Speed Index: 10.0 s

    10.0 s

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

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

    +63%

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

  • Total Blocking Time: 326 ms

    326 ms

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

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

    +12%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 96 ms to 111 ms 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: 2.0 s

    2.0 s

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

  • Real-user INP: 132 ms

    132 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 576 ms

    576 ms

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

  • Cumulative Layout Shift: 0.014

    0.014

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

Images and page weight

2 to fix60
  • Page weight: 7.9 MB in 219 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 219 requests on a phone: images 5.4 MB (47), scripts 1.3 MB (71) and fonts 645 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    24 KiB

    1 image is downloaded at several times the size a phone draws it, for example maxresdefault.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 24 KiB.

  • 2 images in older formats

    2 images (197 KiB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (144 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.25 g

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

Accessibility

5 to fixGoogle 8993
  • 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.

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

  • Frames without titles

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

  • ARIA role should be appropriate for the element (6 elements)

    ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h3 → h5 and h3 → h5), 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).

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Materials Handling Equipment & Asset Management Services - Briggs Equipment”.

  • 18 links with vague text

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

  • 189 internal links, 14 external

    The homepage links to 189 pages on briggsequipment.co.uk and 14 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Hire powered access or materials handling equipment across the UK. With nationwide coverage, we offer machine servicing…”.

  • One H1 headline

    Your main headline reads: “The UK's number one provider of materials handling equipment and engineering services”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, VideoObject and WebPage.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.briggsequipment.co.uk/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.briggsequipment.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 4 pages slow to respond

    https://www.briggsequipment.co.uk/machines, https://www.briggsequipment.co.uk/machines/materials-handling-equipment, https://www.briggsequipment.co.uk/machines/powered-access-equipment and https://www.briggsequipment.co.uk/machines/cleaning-equipment took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187263187&tm=gtm002&Ver=2&mid=13b2fba1-4656-4cdb-9695-03680f18120d&bo=2&sid=bb7ce550d0f211f18a87cdbfc23e8efc&vid=bb7d2070d0f211f1a8626d2e04fac3c1&vids=1&msclkid=N&gtm_.

  • 17 small tap targets

    17 of 51 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 “jQuery is not defined”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

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

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “Order Pickers” and “Learn More”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 12 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 1 more (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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies (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 briggsequipment.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

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on briggsequipment.co.uk, including 18 speed issues, 2 SEO issues and 1 conversion gap. 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