getsprints.com website review

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

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

8 third-party services load with your homepage (Shopify, Accessibe Accessibility Overlay and Klaviyo and others), adding 1.7 MB and 1.2 s of main-thread time.

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

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

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

27 images could be 702 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

12 KiB could be saved by minifying JavaScript.

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.

3 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

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

Your largest element takes 3.9 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 3.8 s (Speed Index). Good is under 3.4 s.

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

Your homepage downloads 5.6 MB in 420 requests on a phone: images 2.6 MB (64), scripts 1.5 MB (99) and other files 1.2 MB (239). Under 2 MB keeps phones on slow connections fast.

MicrosoftTeams-image_348.png weighs 577 KiB. On a phone connection a single image that size takes seconds.

13_39dc437e-68c3-4350-b347-2485b1734dca.png 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).

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

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

4 tap targets are too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 22 elements on the page fail 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.

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

There are 2 <h1> headlines (“” and “Sprints — Running & Athletic Apparel, Gear, and A…”). One clear main headline is easier for people and search engines.

The homepage links to 284 pages on getsprints.com and 6 external pages.

/pages/gift, /collections/socks, /pages/shop-final-sale, /collections/swag, /collections/hats and /collections/hyperg and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/gift, /collections/all-hats, /collections/towel_june22, /pages/all-womens-gear-landing-page, /pages/all-mens-gear-landing-page and /pages/sling-it-lander-2025 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/gift, /pages/all-womens-gear-landing-page, /pages/all-mens-gear-landing-page, /pages/sling-it-lander-2025, /pages/shop-final-sale and /collections/m6sh-hats have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 115 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 SyntaxError: Invalid or unexpected token”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://instagram.com/getsprints.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

getsprints.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

getsprints.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 20 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be getsprints.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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