Website review, no card needed

forshaw.com logo

forshaw.com website review

Visit site (opens in a new tab)Reviewed 24 October 202649 issues · 74 checks

This review found 49 issues worth fixing on forshaw.com, 20 of them high impact, across 74 checks. The most urgent: improve image delivery. 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.3 s2.0 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.9 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.2 s
Sep 19, 20262.4 s
Sep 26, 20262.6 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
212 ms108 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026136 ms
May 9, 2026124 ms
May 16, 2026127 ms
May 23, 2026137 ms
May 30, 2026174 ms
Jun 6, 2026187 ms
Jun 13, 2026193 ms
Jun 20, 2026193 ms
Jun 27, 2026187 ms
Jul 4, 2026200 ms
Jul 11, 2026195 ms
Jul 18, 2026192 ms
Jul 25, 2026189 ms
Aug 1, 2026176 ms
Aug 8, 2026170 ms
Aug 15, 2026156 ms
Aug 22, 2026155 ms
Aug 29, 2026171 ms
Sep 5, 2026150 ms
Sep 12, 2026144 ms
Sep 19, 2026145 ms
Sep 26, 2026143 ms
Oct 3, 2026146 ms
Oct 10, 2026120 ms
Oct 17, 2026120 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 forshaw.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. forshaw.com at 1.0 s1.0 s
  2. forshaw.com at 2.1 s2.1 s
  3. forshaw.com at 3.1 s3.1 s
  4. forshaw.com at 4.1 s4.1 s
  5. forshaw.com at 5.1 s5.1 s
  6. forshaw.com at 6.2 s6.2 s
  7. forshaw.com at 7.2 s7.2 s
  8. forshaw.com at 8.2 s8.2 s

Speed

9 to fix49
  • Improve image delivery

    2.9 s · 1.7 MB

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

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 49

    49/100

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

  • Reduce unused JavaScript

    600 ms · 495 KiB

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

  • Use efficient cache lifetimes

    600 ms · 120 KiB

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

  • Main-thread work: 3.3 s

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

  • 10 long tasks on the main thread

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

  • Google Tag Manager adds 193 ms

    193 ms

    Google Tag Manager costs a phone 193 ms of main-thread work and 475 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,154 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, termly.io and Dynatrace and others), adding 786 KiB and 443 ms of main-thread time.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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 JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 60 ms

    60 ms

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

Core Web Vitals

11 to fix0
  • 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.

  • Real-user CLS: 1.22

    1.22

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

  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (5.8 s).

  • Speed Index: 12.5 s

    12.5 s

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

  • Time to Interactive: 16.0 s

    16.0 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

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

    +23%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • 42 images without width and height

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

  • Total Blocking Time: 351 ms

    351 ms

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

  • Tap response (INP) held steady for real visitors

    -8%

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

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

5 to fix26
  • Page weight: 4.1 MB in 145 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 145 requests on a phone: images 2.0 MB (14), scripts 1.7 MB (111) and HTML 189 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    august website banners 2026_zoecon-49.png weighs 834 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    780 KiB

    1 image is downloaded at several times the size a phone draws it, for example august website banners 2026_zoecon-49.png at 4,226 px wide, shown at 358 px. Resized copies would save about 780 KiB.

  • 8 images in older formats

    8 images (2.3 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.

  • An image on the first screen is lazy-loaded

    hero-banner-responsive.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).

  • 1 image below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.17 g

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

Accessibility

6 to fixGoogle 8894
  • 15 text elements with low contrast

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

  • Heading levels should only increase by one (3 elements)

    Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

  • 6 links without text

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

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

SEO

9 to fixGoogle 9250
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

2 checks passed
  • 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.forshaw.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 859 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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.forshaw.com/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.

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

Best practices

2 to fixGoogle 9687
  • 12 small tap targets

    12 of 35 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 “Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 859 words of visible text.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 13 cookies set on arrival

    13

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

  • 9 other companies contacted

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

1 checks passed
  • Consent tool: Termly

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

Upkeep, stack and company

Stack

CMS
Sana Commerce
Framework
jQuery
Analytics
Google 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 49 issues on forshaw.com, including 20 speed issues, 9 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