Website review, no card needed

tecsosport.com logo

tecsosport.com website review

Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 87 checks

This review found 40 issues worth fixing on tecsosport.com, 17 of them high impact, across 87 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
3.7 s2.7 sMay 16Oct 312.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.2 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.5 s
Aug 15, 20263.5 s
Sep 19, 20263.1 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.1 s
Oct 24, 20262.9 s
Oct 31, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
184 ms143 msMay 16Oct 31161 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026148 ms
May 23, 2026148 ms
May 30, 2026150 ms
Jun 6, 2026153 ms
Jun 13, 2026156 ms
Jun 20, 2026160 ms
Jun 27, 2026167 ms
Jul 4, 2026166 ms
Jul 11, 2026169 ms
Jul 18, 2026169 ms
Jul 25, 2026172 ms
Aug 1, 2026179 ms
Aug 8, 2026173 ms
Aug 15, 2026171 ms
Sep 19, 2026158 ms
Sep 26, 2026162 ms
Oct 3, 2026164 ms
Oct 10, 2026161 ms
Oct 17, 2026166 ms
Oct 24, 2026162 ms
Oct 31, 2026161 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 tecsosport.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tecsosport.com at 0.6 s0.6 s
  2. tecsosport.com at 1.2 s1.2 s
  3. tecsosport.com at 1.9 s1.9 s
  4. tecsosport.com at 2.5 s2.5 s
  5. tecsosport.com at 3.1 s3.1 s
  6. tecsosport.com at 3.7 s3.7 s
  7. tecsosport.com at 4.3 s4.3 s
  8. tecsosport.com at 4.9 s4.9 s

Speed

11 to fix30
  • Reduce unused JavaScript

    2.7 s · 580 KiB

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

  • gtranslate.net adds 1.8 s

    1.8 s

    gtranslate.net costs a phone 1.8 s of main-thread work and 47 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 5.4 s

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

  • 3,622 HTML elements

    The page has 3,622 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 (gtranslate.net, Google Tag Manager and Shopify and others), adding 1.5 MB and 2.9 s of main-thread time.

  • Improve image delivery

    950 ms · 227 KiB

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

  • Use efficient cache lifetimes

    700 ms · 170 KiB

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

  • Google Tag Manager adds 365 ms

    365 ms

    Google Tag Manager costs a phone 365 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.

  • Shopify adds 240 ms

    240 ms

    Shopify costs a phone 240 ms of main-thread work and 626 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

    250 ms · 24 KiB

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    127 KiB

    About 127 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

9 to fix33
  • 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 LCP: 4.0 s

    4.0 s

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

  • Real-user CLS: 0.65

    0.65

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

  • Largest Contentful Paint: 17.1 s

    17.1 s

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

  • Time to Interactive: 17.1 s

    17.1 s

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

  • Cumulative Layout Shift: 0.604

    0.604

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Total Blocking Time: 528 ms

    528 ms

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

  • 21 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

4 checks passed
  • Real-user INP: 175 ms

    175 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 585 ms

    585 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 189 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 189 requests on a phone: scripts 1.4 MB (73), other files 810 KiB (68) and images 567 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.86 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 102.6 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

9 to fixGoogle 8988
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

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

  • 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 (118 elements)

    All page content should be contained by landmarks: 118 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 23 links without text

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

  • 8 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 8586
  • Title is short (10 characters)

    Your title is only 10 characters: “TECSOSPORT”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“TECSOSPORT” and “Cerca”). One clear main headline is easier for people and search engines.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 190 internal links, 17 external

    The homepage links to 190 pages on tecsosport.com and 17 external pages.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Abbigliamento tecnico per lo sport: intimo sportivo, calze, ciclismo, running, trekking. Scopri la nuova collezione e a…”.

  • Canonical URL set

    The canonical URL is https://www.tecsosport.com/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://www.tecsosport.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.tecsosport.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.tecsosport.com/customer_authentication/redirect 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.tecsosport.com/pages/k-band, https://www.tecsosport.com/customer_authentication/redirect and https://www.tecsosport.com/pages/running have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.tecsosport.com/customer_authentication/redirect 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 53 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cookies.digitalhost.it/cookieconsent.css' from origin 'https://www.tecsosport.com'…”.

2 checks passed
  • Tap targets are thumb-sized

    27 of 32 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 577 words of copy

    The homepage carries about 577 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: “Back to the shop”.

  • 1 call to action

    The homepage has 1 call to action, for example “[email protected]”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 123 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (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.

  • 30 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on tecsosport.com, including 20 speed issues and 3 SEO 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