Website review, no card needed
standardandstrange.com website review
Visit site (opens in a new tab)Reviewed 8 November 202627 issues · 78 checks
This review found 27 issues worth fixing on standardandstrange.com, 7 of them high impact, across 78 checks. The most urgent: page weight: 5.2 MB in 455 requests. 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
84B- #19,824 of 109,117 reviewed websitesbeats 77%
- #12,887 of 61,799 online storesbeats 73%
- #12,517 of 56,377 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 884 ms |
| Jun 6, 2026 | 835 ms |
| Jun 13, 2026 | 841 ms |
| Jun 20, 2026 | 837 ms |
| Jun 27, 2026 | 945 ms |
| Jul 4, 2026 | 967 ms |
| Jul 11, 2026 | 946 ms |
| Jul 18, 2026 | 932 ms |
| Jul 25, 2026 | 913 ms |
| Aug 1, 2026 | 916 ms |
| Aug 8, 2026 | 901 ms |
| Aug 15, 2026 | 893 ms |
| Aug 22, 2026 | 881 ms |
| Aug 29, 2026 | 889 ms |
| Sep 5, 2026 | 898 ms |
| Sep 12, 2026 | 898 ms |
| Sep 19, 2026 | 902 ms |
| Sep 26, 2026 | 878 ms |
| Oct 3, 2026 | 869 ms |
| Oct 10, 2026 | 901 ms |
| Oct 17, 2026 | 910 ms |
| Oct 24, 2026 | 913 ms |
| Oct 31, 2026 | 897 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 89 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 93 ms |
| Jun 6, 2026 | 93 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 92 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 100 ms |
| Sep 19, 2026 | 100 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 101 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 96 ms |
| Oct 31, 2026 | 95 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.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.0 s
3.5 s
Speed
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
350 ms · 341 KiB10 images could be 341 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 253 ms. During a long task the page ignores taps.
Shopify adds 195 ms
195 msShopify costs a phone 195 ms of main-thread work and 493 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,291 HTML elements
The page has 2,291 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 (Shopify, Klaviyo and Attentive and others), adding 983 KiB and 473 ms of main-thread time.
Reduce unused JavaScript
150 ms · 133 KiBAbout 133 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
205 KiB19 files are served with short cache lifetimes, so returning visitors download them again (205 KiB).
Reduce unused CSS
150 ms · 38 KiBAbout 38 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.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 213 ms
213 msScripts block taps and scrolling for 213 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 89 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 432 ms
432 msReal visitors wait 432 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 455 requests
5.2 MBYour homepage downloads 5.2 MB in 455 requests on a phone: images 2.6 MB (23), other files 1.3 MB (250) and scripts 1,011 KiB (158). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Summer_26_Banner-7_32766db6-734c-4d34-af13-272730213d8e.jpg 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 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.6 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
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
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.
31 links without text
31 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 92 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 1 more 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
262 internal links, 7 external
The homepage links to 262 pages on standardandstrange.com and 7 external pages.
7 checks passed
Meta description: 80 characters
Your meta description is 80 characters: “Home to the absolute best in denim, boots, and more from Japan, USA, and Europe.”.
One H1 headline
Your main headline reads: “Standard & Strange”.
Title: 45 characters
Your title is a healthy 45 characters: “Standard & Strange - Own Fewer, Better Things”.
Canonical URL set
The canonical URL is https://standardandstrange.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://standardandstrange.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,381 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://standardandstrange.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://standardandstrange.com/collections/new-in-the-shop, https://standardandstrange.com/blogs/standard-strange-stories, https://standardandstrange.com/collections/1st-pat-rn, https://standardandstrange.com/collections/american-trench, https://standardandstrange.com/collections/and-wander and https://standardandstrange.com/collections/arch-support-project and 8 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 167 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.
2 checks passed
Tap targets are thumb-sized
37 of 45 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 251 words of copy
The homepage carries about 251 words of visible text.
2 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Last Call”, “Last CallLast Call” and “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
26 other companies contacted
Loading the homepage contacts 26 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 standardandstrange.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Attentive · Loop Returns · Restockrocket · nofraud.com · klarnaservices.com · cloudfront.net · attn.tv · shareasale.com · standardandstrange.com · adscale.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Oakland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on standardandstrange.com, including 11 speed issues, 2 SEO issues and 4 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.