Website review, no card needed

jrtrolleys.co.uk logo

jrtrolleys.co.uk website review

Visit site (opens in a new tab)Reviewed 13 November 202633 issues · 61 checks

This review found 33 issues worth fixing on jrtrolleys.co.uk, 9 of them high impact, across 61 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of jrtrolleys.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jrtrolleys.co.uk at 0.4 s0.4 s
  2. jrtrolleys.co.uk at 0.8 s0.8 s
  3. jrtrolleys.co.uk at 1.1 s1.1 s
  4. jrtrolleys.co.uk at 1.5 s1.5 s
  5. jrtrolleys.co.uk at 1.9 s1.9 s
  6. jrtrolleys.co.uk at 2.3 s2.3 s
  7. jrtrolleys.co.uk at 2.6 s2.6 s
  8. jrtrolleys.co.uk at 3.0 s3.0 s

Speed

6 to fix81
  • Use efficient cache lifetimes

    4.3 s · 3.0 MB

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

  • Improve image delivery

    3.3 s · 1.4 MB

    22 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

  • Mobile performance score: 81

    81/100

    Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

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

  • Font display

    400 ms

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

  • Reduce unused JavaScript

    300 ms · 47 KiB

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

  • Reduce unused CSS

    150 ms · 17 KiB

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

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

2 checks passed
  • Main-thread work: 0.2 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

4 to fix77
  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Manufacturers of Trolleys, Racks, Trays, Tables and Plastic…”.

  • 34 images without width and height

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

  • Time to Interactive: 4.8 s

    4.8 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • 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

4 to fix48
  • 5 images far larger than shown

    635 KiB

    5 images are downloaded at several times the size a phone draws them, for example trolleys-double.jpg at 600 px wide, shown at 78 px. Resized copies would save about 635 KiB.

  • Page weight: 3.0 MB in 41 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 41 requests on a phone: images 2.9 MB (36), scripts 68 KiB (2) and fonts 32 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 19 images in older formats

    19 images (1.4 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.

  • 17 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.85 g

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

Accessibility

4 to fixGoogle 8793
  • 35 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 6 links without text

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

  • Headings skip levels

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

1 checks passed
  • 31 automated accessibility rules passed

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

SEO

7 to fixGoogle 8266
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (15 characters)

    Your title is only 15 characters: “JR Trolleys Ltd”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

    There is no robots.txt at jrtrolleys.co.uk/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 10 internal links, 7 external

    The homepage links to 10 pages on jrtrolleys.co.uk and 7 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Manufacturers of Trolleys, Racks, Trays, Tables and Plastic Containers”.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • 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 analytics detected

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

  • No opening hours

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

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

    The homepage carries about 600 words of visible text.

2 checks passed
  • Direct contact links

    Visitors can reach you directly: 9 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

  • 1 cookie set on arrival

    1

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

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

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

Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on jrtrolleys.co.uk, including 10 speed issues, 7 SEO issues and 5 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