Website review, no card needed

altrarunning.com logo

altrarunning.com website review

Visit site (opens in a new tab)Reviewed 19 October 202642 issues · 90 checks

This review found 42 issues worth fixing on altrarunning.com, 16 of them high impact, across 90 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s3.5 sMay 2Oct 173.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20263.8 s
May 16, 20263.9 s
May 23, 20264.0 s
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20264.0 s
Jul 11, 20263.9 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.7 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.8 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
340 ms249 msMay 2Oct 17297 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026259 ms
May 9, 2026264 ms
May 16, 2026275 ms
May 23, 2026288 ms
May 30, 2026303 ms
Jun 6, 2026304 ms
Jun 13, 2026300 ms
Jun 20, 2026293 ms
Jun 27, 2026283 ms
Jul 4, 2026282 ms
Jul 11, 2026286 ms
Jul 18, 2026288 ms
Jul 25, 2026294 ms
Aug 1, 2026296 ms
Aug 8, 2026298 ms
Aug 15, 2026304 ms
Aug 22, 2026312 ms
Aug 29, 2026323 ms
Sep 5, 2026329 ms
Sep 12, 2026324 ms
Sep 19, 2026320 ms
Sep 26, 2026310 ms
Oct 3, 2026296 ms
Oct 10, 2026291 ms
Oct 17, 2026297 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 altrarunning.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. altrarunning.com at 1.0 s1.0 s
  2. altrarunning.com at 2.0 s2.0 s
  3. altrarunning.com at 3.0 s3.0 s
  4. altrarunning.com at 4.1 s4.1 s
  5. altrarunning.com at 5.1 s5.1 s
  6. altrarunning.com at 6.1 s6.1 s
  7. altrarunning.com at 7.1 s7.1 s
  8. altrarunning.com at 8.1 s8.1 s

Speed

14 to fix32
  • Use efficient cache lifetimes

    1.6 s · 3.8 MB

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

  • Main-thread work: 10.3 s

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

  • Mobile performance score: 32

    32/100

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

  • 3,924 HTML elements

    The page has 3,924 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, Dynatrace and Quantum Metric and others), adding 3.6 MB and 2.4 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 804 ms

    804 ms

    Google Tag Manager costs a phone 804 ms of main-thread work and 581 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.

  • Dynatrace adds 644 ms

    644 ms

    Dynatrace costs a phone 644 ms of main-thread work and 117 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.

  • Render-blocking requests

    600 ms

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

  • 20 long tasks on the main thread

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

  • Improve image delivery

    547 KiB

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

  • Quantum Metric adds 332 ms

    332 ms

    Quantum Metric costs a phone 332 ms of main-thread work and 103 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.

  • Yotpo adds 92 ms

    92 ms

    Yotpo costs a phone 92 ms of main-thread work and 2.0 MB 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.

  • Shopify adds 119 ms

    119 ms

    Shopify costs a phone 119 ms of main-thread work and 324 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.

  • Reduce unused CSS

    150 ms · 100 KiB

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

  • Legacy JavaScript

    77 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    10 KiB

    10 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: 40 ms

    40 ms

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

Core Web Vitals

9 to fix67
  • 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 FCP: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 14.2 s

    14.2 s

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

  • Time to Interactive: 44.5 s

    44.5 s

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

  • Speed Index: 14.3 s

    14.3 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user INP: 166 ms

    166 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 10.4 MB in 598 requests

    10.4 MB

    Your homepage downloads 10.4 MB in 598 requests on a phone: images 5.7 MB (180), scripts 3.4 MB (152) and other files 839 KiB (192). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    BrandMoment_OurStory_16x9_a7ef74dd-af5f-4ddc-a4a7-73205db074 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).

  • About 2.9 g of CO₂ per visit

    2.94 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9495
  • 3 text elements with low contrast

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

  • 1 image without alt text

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

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 7792
  • Structured data has 1 problem

    Structured data found (Brand, OnlineStore, WebPage and WebSite) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected end of JSON input)”.

  • 1 link crawlers can't follow

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

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 183 internal links, 2 external

    The homepage links to 183 pages on altrarunning.com and 2 external pages.

6 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Altra was founded with a desire to find a better shoe for road and trail running. Experience the difference of our Foot…”.

  • One H1 headline

    Your main headline reads: “Experience Wild 3+ GTX”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Running Shoes with FootShape™ Comfort | Altra Running US”.

  • Canonical URL set

    The canonical URL is https://www.altrarunning.com/en-us.

  • 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.altrarunning.com/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    24%

    A phone browser shows 1,818 words, but the HTML your server sends has only 439. 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.

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: 5 of 6 facts

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

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.altrarunning.com/en-us/pages/women is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.altrarunning.com/en-us/pages/select-your-location, https://www.altrarunning.com/en-us/pages/shoe-finder and https://www.altrarunning.com/en-us/pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.altrarunning.com/en-us/pages/customer-service, https://www.altrarunning.com/en-us/collections/new-arrivals, https://www.altrarunning.com/en-us/pages/shoe-finder, https://www.altrarunning.com/en-us/pages/wishlist and https://www.altrarunning.com/en-us/pages/size-chart have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5488
  • 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.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    162 of 184 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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 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.

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

  • About 1,818 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Track Order” and “Shop All”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Track Order”, “Shop All” and “Shop Now”.

  • 9 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Tag Manager, Meta Pixel and Pinterest Tag and 3 mores (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.

  • 33 cookies set on arrival

    33

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

  • 60 other companies contacted

    Loading the homepage contacts 60 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 altrarunning.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager

Company

Founded
2009
Headquarters
Logan

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on altrarunning.com, including 23 speed issues, 3 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