tenniszon.com website review

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

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

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

25 images could be 4.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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.

8 third-party services load with your homepage (Google CDN, Shopify and Klaviyo and others), adding 2.7 MB and 1.1 s of main-thread time.

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

Google CDN costs a phone 560 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.

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

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

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 10.5 MB in 492 requests on a phone: images 5.4 MB (40), scripts 2.6 MB (184) and other files 1.8 MB (202). Under 2 MB keeps phones on slow connections fast.

3 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example IMG_7188_copie.webp at 3,024 px wide, shown at 360 px. Resized copies would save about 4.5 MB.

11 images (6.1 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 further down the page (6.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

There are 2 <h1> headlines (“” and “Read all the tips and advices fromour experts.”). One clear main headline is easier for people and search engines.

Structured data found (Organization, SportingGoodsStore and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("tenniszon.com")”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 747 pages on tenniszon.com and 19 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

https://tenniszon.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tenniszon.com/collections/all, https://tenniszon.com/customer_authentication/redirect, https://tenniszon.com/policies/shipping-policy, https://tenniszon.com/products/tenniszon-gift-card, https://tenniszon.com/pages/contact and https://tenniszon.com/pages/subscribe-to-our-newsletter and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://tenniszon.com/collections/all, https://tenniszon.com/customer_authentication/redirect, https://tenniszon.com/policies/shipping-policy, https://tenniszon.com/products/tenniszon-gift-card, https://tenniszon.com/pages/faq and https://tenniszon.com/pages/contact and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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

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.

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