Website review, no card needed

sportler.com logo

sportler.com website review

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

This review found 35 issues worth fixing on sportler.com, 11 of them high impact, across 79 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
1.5 s1.2 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
198 ms166 msMay 9Oct 24183 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026172 ms
May 16, 2026170 ms
May 23, 2026171 ms
May 30, 2026174 ms
Jun 6, 2026178 ms
Jun 13, 2026183 ms
Jun 20, 2026186 ms
Jun 27, 2026186 ms
Jul 4, 2026187 ms
Jul 11, 2026188 ms
Jul 18, 2026189 ms
Jul 25, 2026190 ms
Aug 1, 2026193 ms
Aug 8, 2026194 ms
Aug 15, 2026193 ms
Aug 22, 2026192 ms
Aug 29, 2026188 ms
Sep 5, 2026187 ms
Sep 12, 2026188 ms
Sep 19, 2026189 ms
Sep 26, 2026189 ms
Oct 3, 2026188 ms
Oct 10, 2026186 ms
Oct 17, 2026183 ms
Oct 24, 2026183 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 sportler.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix47
  • Reduce unused JavaScript

    1.5 s · 428 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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 (styla.com, iubenda and Google Tag Manager and others), adding 1.5 MB and 802 ms of main-thread time.

  • Render-blocking requests

    700 ms

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

  • styla.com adds 501 ms

    501 ms

    styla.com costs a phone 501 ms of main-thread work and 619 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.

  • Use efficient cache lifetimes

    150 ms · 409 KiB

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

  • Reduce unused CSS

    460 ms · 50 KiB

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

  • Main-thread work: 3.4 s

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

  • 12 long tasks on the main thread

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

  • 2,162 HTML elements

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

  • userway.org adds 78 ms

    78 ms

    userway.org costs a phone 78 ms of main-thread work and 488 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.

  • Legacy JavaScript

    150 ms · 21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Improve image delivery

    18 KiB

    1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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: 11 ms

    11 ms

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

Core Web Vitals

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

    7.6 s

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

  • Time to Interactive: 17.0 s

    17.0 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Total Blocking Time: 675 ms

    675 ms

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

  • Real-user INP: 435 ms

    435 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

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

    +10%

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 543 ms

    543 ms

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

  • Cumulative Layout Shift: 0.029

    0.029

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

Images and page weight

2 to fix64
  • Page weight: 6.0 MB in 99 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 99 requests on a phone: images 4.2 MB (27), scripts 1.1 MB (29) and other files 509 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1761299073566_c1a80d2d-9d22-4649-99da-dbdbb072e85e 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 in older formats

    1 image (48 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 1.7 g of CO₂ per visit

    1.70 g

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

1 checks passed
  • 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 fix94
  • 11 images without alt text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

SEO

3 to fixGoogle 10088
  • No structured data

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

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at sportler.com/robots.txt, the first file search crawlers ask for.

  • Open Graph partly set

    Open Graph is missing 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.

  • 300 internal links, 21 external

    The homepage links to 300 pages on sportler.com and 21 external pages.

4 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Negozio di articoli sportivi. Trekking, Sci, Running, Ciclismo, Fitness. Tutto per il tuo Sport preferito ► Sportler: B…”.

  • One H1 headline

    Your main headline reads: “OFFERTE HALLOWEEN DA BRIVIDO”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Sportler | Abbigliamento Sportivo e Articoli Sportivi”.

  • Canonical URL set

    The canonical URL is https://www.sportler.com/it.

AI search readiness

1 to fix81
  • 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.sportler.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
  • Text is in the HTML

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

Other pages

2 to fix70
  • 14 linked pages are broken

    Your homepage links to https://www.sportler.com/it, https://www.sportler.com/mysportler/imieidati, https://www.sportler.com/mysportler/punti, https://www.sportler.com/mysportler/buoni, https://www.sportler.com/mysportler/acquisti and https://www.sportler.com/rientro and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without an H1

    https://www.sportler.com/it/lp/stores has 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 191 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 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 'indexOf')”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    257 of 267 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 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 1,101 words of copy

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

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “DOWNLOAD APP”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 12 other companies contacted

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

2 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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

Upkeep, stack and company

Stack

Hosting
Fastly

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 sportler.com, including 19 speed issues, 3 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