Website review, no card needed

4endurance.com logo

4endurance.com website review

Visit site (opens in a new tab)Reviewed 31 October 202635 issues · 82 checks

This review found 35 issues worth fixing on 4endurance.com, 11 of them high impact, across 82 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
1.9 s1.7 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
159 ms116 msMay 9Oct 24154 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026121 ms
May 16, 2026121 ms
May 23, 2026121 ms
May 30, 2026124 ms
Jun 6, 2026125 ms
Jun 13, 2026127 ms
Jun 20, 2026128 ms
Jun 27, 2026129 ms
Jul 4, 2026131 ms
Jul 11, 2026132 ms
Jul 18, 2026133 ms
Jul 25, 2026133 ms
Aug 1, 2026133 ms
Aug 8, 2026135 ms
Aug 15, 2026135 ms
Aug 22, 2026136 ms
Aug 29, 2026138 ms
Sep 5, 2026137 ms
Sep 12, 2026139 ms
Sep 19, 2026139 ms
Sep 26, 2026141 ms
Oct 3, 2026147 ms
Oct 10, 2026153 ms
Oct 17, 2026153 ms
Oct 24, 2026154 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 4endurance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix56
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused JavaScript

    300 ms · 602 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Klaviyo and others), adding 1.4 MB and 725 ms of main-thread time.

  • Improve image delivery

    150 ms · 464 KiB

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

  • Use efficient cache lifetimes

    200 ms · 307 KiB

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

  • Reduce unused CSS

    300 ms · 48 KiB

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

  • Main-thread work: 3.0 s

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

  • Google Tag Manager adds 229 ms

    229 ms

    Google Tag Manager costs a phone 229 ms of main-thread work and 494 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,617 HTML elements

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

  • Klaviyo adds 132 ms

    132 ms

    Klaviyo costs a phone 132 ms of main-thread work and 355 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.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    38 KiB

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

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 38 ms

    38 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 23.9 s

    23.9 s

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

  • Cumulative Layout Shift: 0.94

    0.94

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

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

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

    +27%

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

  • Speed Index: 4.8 s

    4.8 s

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

  • 18 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

8 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: 1.9 s

    1.9 s

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

  • Real-user INP: 172 ms

    172 ms

    Real visitors wait 172 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.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: 528 ms

    528 ms

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

  • Total Blocking Time: 164 ms

    164 ms

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

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

Images and page weight

4 to fix43
  • Page weight: 5.9 MB in 365 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 365 requests on a phone: other files 2.6 MB (213), scripts 1.8 MB (88) and images 1.3 MB (50). Under 2 MB keeps phones on slow connections fast.

  • 19 images in older formats

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

  • 10 images below the first screen load straight away

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

  • 6 images far larger than shown

    343 KiB

    6 images are downloaded at several times the size a phone draws them, for example 4Endurance-product-categories-fat-burners.webp at 800 px wide, shown at 173 px. Resized copies would save about 343 KiB.

  • About 1.7 g of CO₂ per visit

    1.66 g

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

Accessibility

8 to fixGoogle 8090
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 27 text elements with low contrast

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

  • 5 tap targets too small

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

  • 53 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

Google 92100
  • 205 internal links, 31 external

    The homepage links to 205 pages on 4endurance.com and 31 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Get everything you need for cycling, running, swimming, and other sports: energy gels, isotonic sports drinks, recovery…”.

  • One H1 headline

    Your main headline reads: “Shop Endurance Nutrition & Supplements”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Nutrition for Endurance Athletes | 4Endurance Europe”.

  • Canonical URL set

    The canonical URL is https://4endurance.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, OnlineStore and Organization.

  • 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://4endurance.com/sitemap.xml.

AI search readiness

100
4 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,384 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://4endurance.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

5 to fixGoogle 6967
  • 1 broken image

    1 image failed to load on a phone, for example https://4endurance.com/.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Logged exception (this may happen if you have tried to edit the code without properly adjusting the JavaScript): Cannot…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 666 words of visible text.

6 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 “Shop All”, “Shop our products” and “Join Our Ambassador Program”.

  • 17 short forms

    17 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 29 testimonial or review blocks, 12 customer or partner logos and 8 trust badges.

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 18 cookies set on arrival

    18

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

  • 42 other companies contacted

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

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on 4endurance.com, including 17 speed issues. 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