Website review, no card needed

namedsport.com logo

namedsport.com website review

Visit site (opens in a new tab)Reviewed 18 October 202643 issues · 86 checks

This review found 43 issues worth fixing on namedsport.com, 17 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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.0 s2.4 sApr 25Oct 103.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.7 s
May 2, 20262.7 s
May 9, 20262.6 s
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20263.2 s
Jun 20, 20263.4 s
Jun 27, 20263.5 s
Jul 4, 20263.8 s
Jul 11, 20263.7 s
Jul 18, 20263.5 s
Jul 25, 20263.2 s
Aug 1, 20262.8 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.2 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
223 ms181 msApr 25Oct 10197 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026192 ms
May 2, 2026194 ms
May 9, 2026193 ms
May 16, 2026189 ms
May 23, 2026186 ms
May 30, 2026187 ms
Jun 6, 2026190 ms
Jun 13, 2026197 ms
Jun 20, 2026206 ms
Jun 27, 2026213 ms
Jul 4, 2026215 ms
Jul 11, 2026213 ms
Jul 18, 2026211 ms
Jul 25, 2026204 ms
Aug 1, 2026202 ms
Aug 8, 2026203 ms
Aug 15, 2026206 ms
Aug 22, 2026215 ms
Aug 29, 2026216 ms
Sep 5, 2026218 ms
Sep 12, 2026211 ms
Sep 19, 2026203 ms
Sep 26, 2026202 ms
Oct 3, 2026196 ms
Oct 10, 2026197 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 namedsport.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. namedsport.com at 1.9 s1.9 s
  2. namedsport.com at 3.7 s3.7 s
  3. namedsport.com at 5.6 s5.6 s
  4. namedsport.com at 7.4 s7.4 s
  5. namedsport.com at 9.3 s9.3 s
  6. namedsport.com at 11.2 s11.2 s
  7. namedsport.com at 13.0 s13.0 s
  8. namedsport.com at 14.9 s14.9 s

Speed

12 to fix45
  • Reduce unused JavaScript

    2.6 s · 920 KiB

    About 920 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

  • Use efficient cache lifetimes

    2.5 s · 508 KiB

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

  • Render-blocking requests

    2.9 s

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

  • Font display

    1.7 s

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

  • Minify JavaScript

    1.1 s · 253 KiB

    253 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45 (desktop: 36). 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 CDN, Google Tag Manager and cookiebot.eu and others), adding 2.1 MB and 1.3 s of main-thread time.

  • Improve image delivery

    750 ms · 214 KiB

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

  • Reduce unused CSS

    750 ms · 169 KiB

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

  • Google CDN adds 429 ms

    429 ms

    Google CDN costs a phone 429 ms of main-thread work and 1.1 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.

  • Google Tag Manager adds 409 ms

    409 ms

    Google Tag Manager costs a phone 409 ms of main-thread work and 722 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.4 s

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

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 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.

  • Largest Contentful Paint: 42.0 s

    42.0 s

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

  • Speed Index: 21.7 s

    21.7 s

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

  • Time to Interactive: 44.8 s

    44.8 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

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

    1.1 s

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

  • Total Blocking Time: 551 ms

    551 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

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

    +14%

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

4 checks passed
  • 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.06

    0.06

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • 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

3 to fix45
  • Page weight: 8.5 MB in 345 requests

    8.5 MB

    Your homepage downloads 8.5 MB in 345 requests on a phone: images 4.1 MB (20), scripts 3.0 MB (251) and other files 741 KiB (37). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    StarWhey_900x900.png weighs 540 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (540 KiB) is 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.

  • About 2.4 g of CO₂ per visit

    2.41 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9294
  • 1 text element with low contrast

    1 text element doesn'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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 10071
  • No H1 headline

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

  • Title is short (21 characters)

    Your title is only 21 characters: “NAMEDSPORT> SUPERFOOD”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (275 characters)

    Your meta description is 275 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 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 XML sitemap

    No XML sitemap at https://www.namedsport.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 153 internal links, 19 external

    The homepage links to 153 pages on namedsport.com and 19 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.namedsport.com/en.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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

Other pages

6 to fix69
  • 1 linked page hidden from search

    https://www.namedsport.com/en/catalogsearch/advanced is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages share a title

    https://www.namedsport.com/en?___store=www_en&___from_store=www_it, https://www.namedsport.com/de, https://www.namedsport.com/fr, https://www.namedsport.com/it, https://www.namedsport.com/pt and https://www.namedsport.com/za and 2 others all use the title “NAMEDSPORT> SUPERFOOD”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.namedsport.com/en/mission, https://www.namedsport.com/en/contact, https://www.namedsport.com/en/catalogsearch/advanced, https://www.namedsport.com/en/storelocator, https://www.namedsport.com/en/products/athlete-gear-merchandising.html and https://www.namedsport.com/en/products/energy-bars.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://www.namedsport.com/de, https://www.namedsport.com/fr, https://www.namedsport.com/it, https://www.namedsport.com/pt, https://www.namedsport.com/za and https://www.namedsport.com/es and 1 other use the same meta description. A description written for each page earns more clicks.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.namedsport.com/de, whose canonical is https://www.namedsport.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.namedsport.com/de, https://www.namedsport.com/fr, https://www.namedsport.com/it, https://www.namedsport.com/pt, https://www.namedsport.com/za and https://www.namedsport.com/es and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.namedsport.com/en/products.html took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 3 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Framing 'https://cdn.lightwidget.com/' violates the following report-only Content Security Policy directive: "frame-src…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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.

  • Only about 230 words

    The homepage has only about 230 words of visible text; thin pages give Google and first-time buyers little to go on.

6 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT US” and “Subscribe”.

  • 2 short forms

    2 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: 1 testimonial or review block and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • 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

  • 7 trackers load before any consent

    7

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

  • 14 cookies set on arrival

    14

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

  • 27 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 namedsport.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
Magento

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on namedsport.com, including 21 speed issues, 5 SEO issues and 2 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