signaturelocker.com website review

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

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

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

8 third-party services load with your homepage (hsappstatic.net, Hubspot and Shopify and others), adding 1.5 MB and 842 ms of main-thread time.

About 395 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

hsappstatic.net costs a phone 466 ms of main-thread work and 715 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.

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

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

Hubspot costs a phone 238 ms of main-thread work and 336 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,040 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

Polyfills for old browsers add 14 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.

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

3 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 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ON-DEMAND UNIFORMS AND TEAM STORES”. Most of its time is element render delay (5.8 s).

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

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

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 185 requests on a phone: media 4.0 MB (4), scripts 1.6 MB (83) and images 353 KiB (26). Under 2 MB keeps phones on slow connections fast.

2 images (768 KiB) 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.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 69 characters, so Google will cut it off around 60: “Signature Athletics: Custom Uniforms & Team Stores – Signature Locker”.

There are 3 <h1> headlines (“”, “Custom On-Demand Uniforms And Team Stores” and “”). One clear main headline is easier for people and search engines.

Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization, SportingGoodsStore and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 50 pages on signaturelocker.com and 12 external pages.

There is no https://signaturelocker.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.

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

https://signaturelocker.com/customer_authentication/redirect and https://signaturelocker.com/pages/signature-partner-program are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://signaturelocker.com/customer_authentication/redirect and https://signaturelocker.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://signaturelocker.com/customer_authentication/redirect and https://signaturelocker.com/pages/signature-partner-program have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://signaturelocker.com/cdn/shop/t/124/assets/tiny.content.min.css?v=423562' because i…”.

Chrome logged issues while loading the page (“Cookie”).

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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 731 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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