skatingboutique.com website review

Google Tag Manager costs a phone 1.0 s of main-thread work and 698 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, preordernowapp.com and Shopify and others), adding 2.0 MB and 3.7 s of main-thread time.

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

preordernowapp.com costs a phone 970 ms of main-thread work and 78 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.

About 796 KiB of JavaScript is downloaded but never used on this page.

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

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

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

rebuyengine.com costs a phone 267 ms of main-thread work and 332 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.

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

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

71 KiB could be saved by minifying JavaScript.

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

12 KiB could be saved by minifying CSS.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 297 requests on a phone: scripts 2.1 MB (81), images 923 KiB (40) and other files 917 KiB (160). Under 2 MB keeps phones on slow connections fast.

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

8 dropdowns have no label.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 element hidden from screen readers can still receive keyboard focus.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 274 pages on skatingboutique.com and 13 external pages.

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

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

https://skatingboutique.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://skatingboutique.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97173973&Ver=2&mid=40dd27c8-f475-42db-829c-3257aed1de33&bo=1&sid=6b6c8ab0da9811f18649d36a7c579329&vid=6b6cb2a0da9811f1a117fd9c72ac5d57&vids=1&msclkid=N&pi=918639831&lg.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

4 errors were logged to the browser console while the page loaded, for example “[Myra] No injection target found! Neither app block nor embed selector matched. Options will NOT render. Tried selector…”.

3 images are served at too low a resolution for sharp phone screens.

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.

The homepage shows no opening hours. If customers visit or call, show when.

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 978 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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 23 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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.