Website review, no card needed
aerosoles.com website review
Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 84 checks
This review found 40 issues worth fixing on aerosoles.com, 16 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72C- #96,603 of 124,883 reviewed websitesbeats 19%
- #59,452 of 70,062 online storesbeats 12%
- #55,342 of 63,671 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.9 s |
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 130 ms |
| May 2, 2026 | 134 ms |
| May 9, 2026 | 137 ms |
| May 16, 2026 | 137 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 157 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 136 ms |
| Oct 10, 2026 | 135 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
How it loaded on a phone
0.9 s
1.7 s
2.6 s
3.5 s
4.4 s
5.2 s
6.1 s
7.0 s
Speed
Reduce unused JavaScript
3.1 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 1.8 MB45 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Render-blocking requests
1.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 27
27/100Your mobile performance score is 27 (desktop: 36). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 5.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,667 HTML elements
The page has 4,667 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 (Google Tag Manager, Shopify and Yotpo and others), adding 3.6 MB and 2.9 s of main-thread time.
Improve image delivery
1.0 MB19 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 925 ms
925 msGoogle Tag Manager costs a phone 925 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.
Reduce unused CSS
450 ms · 250 KiBAbout 250 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
600 ms · 51 KiB51 KiB could be saved by minifying JavaScript.
Yotpo adds 498 ms
498 msYotpo costs a phone 498 ms of main-thread work and 797 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 501 ms
501 msShopify costs a phone 501 ms of main-thread work and 670 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
400 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 341 ms. During a long task the page ignores taps.
Kaltura Video Platform adds 255 ms
255 msKaltura Video Platform costs a phone 255 ms of main-thread work and 471 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.
Facebook adds 279 ms
279 msFacebook costs a phone 279 ms of main-thread work and 224 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.
Minify CSS
107 KiB107 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 23.4 s
23.4 sYour largest element takes 23.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A split two-panel lifestyle photograph showcasing a pair of…”.
Time to Interactive: 39.9 s
39.9 sThe page becomes fully interactive after 39.9 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 130 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 516 ms
516 msReal visitors wait 516 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.076
0.076The layout barely moves while loading (CLS 0.076, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 454 requests
7.6 MBYour homepage downloads 7.6 MB in 454 requests on a phone: scripts 4.0 MB (168), images 2.0 MB (36) and other files 898 KiB (209). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
001_Main_Banner_Mobile_360x500_8a3bdd9c-d2fd-407c-8a22-585cf 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).
About 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 259.8 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
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“LIVE FASHIONABLY, MOVE COMFORTABLY”, “WHERE COMFORT MEETS STYLE” and “FALL FOOTWEAR STORIES”). One clear main headline is easier for people and search engines.
197 internal links, 25 external
The homepage links to 197 pages on aerosoles.com and 25 external pages.
6 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Renowned for our comfort technology, AEROSOLES continues to provide engineered comfort and elevated style for every ste…”.
Title: 46 characters
Your title is a healthy 46 characters: “Live Fashionably, Move Comfortably – Aerosoles”.
Canonical URL set
The canonical URL is https://www.aerosoles.com/.
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.aerosoles.com/sitemap.xml.
AI search readiness
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 (1,443 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.aerosoles.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages without a meta description
https://www.aerosoles.com/collections/mens-collection, https://www.aerosoles.com/collections/new-arrivals-heels, https://www.aerosoles.com/collections/new-arrivals-flats-loafers, https://www.aerosoles.com/collections/new-arrivals-boots, https://www.aerosoles.com/collections/new-arrivals-platforms and https://www.aerosoles.com/collections/new-arrivals-mules-clogs and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.aerosoles.com/.
4 small tap targets
4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Bad element for Flickity: null”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 303 words of copy
The homepage carries about 303 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
18 calls to action
The homepage has 18 calls to action, for example “shop all”, “shop all sale” and “shop by size”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, 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.
36 cookies set on arrival
36Opening the homepage sets 36 cookies (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.
68 other companies contacted
Loading the homepage contacts 68 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 aerosoles.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on aerosoles.com, including 25 speed issues, 2 SEO issues and 2 conversion gaps. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.