Website review, no card needed
frame-store.com website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 86 checks
This review found 40 issues worth fixing on frame-store.com, 14 of them high impact, across 86 checks. The most urgent: render-blocking 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
78C- #59,613 of 117,972 reviewed websitesbeats 44%
- #39,183 of 67,058 online storesbeats 36%
- #37,465 of 61,142 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 302 ms |
| May 23, 2026 | 312 ms |
| May 30, 2026 | 312 ms |
| Jun 6, 2026 | 295 ms |
| Jun 13, 2026 | 279 ms |
| Jun 20, 2026 | 271 ms |
| Jun 27, 2026 | 278 ms |
| Jul 4, 2026 | 278 ms |
| Jul 11, 2026 | 278 ms |
| Jul 18, 2026 | 273 ms |
| Jul 25, 2026 | 273 ms |
| Aug 1, 2026 | 279 ms |
| Aug 8, 2026 | 283 ms |
| Aug 15, 2026 | 287 ms |
| Aug 22, 2026 | 306 ms |
| Aug 29, 2026 | 353 ms |
| Sep 5, 2026 | 386 ms |
| Sep 12, 2026 | 412 ms |
| Sep 19, 2026 | 416 ms |
| Sep 26, 2026 | 416 ms |
| Oct 3, 2026 | 420 ms |
| Oct 10, 2026 | 421 ms |
| Oct 17, 2026 | 431 ms |
| Oct 24, 2026 | 421 ms |
| Oct 31, 2026 | 418 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.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
6.0 s
Speed
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.6 s
A phone's processor spends 8.6 s on main-thread work while loading, 5.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,588 HTML elements
The page has 4,588 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 ContentSquare and others), adding 2.2 MB and 2.1 s of main-thread time.
Improve image delivery
800 ms · 973 KiB24 images could be 973 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 1.4 MB45 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Reduce unused JavaScript
1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 928 ms
928 msGoogle Tag Manager costs a phone 928 ms of main-thread work and 719 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 261 ms
261 msShopify costs a phone 261 ms of main-thread work and 619 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.
ContentSquare adds 254 ms
254 msContentSquare costs a phone 254 ms of main-thread work and 196 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.
Reduce unused CSS
150 ms · 119 KiBAbout 119 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need.
Minify JavaScript
40 KiB40 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 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.
Time to Interactive: 43.3 s
43.3 sThe page becomes fully interactive after 43.3 s. Good is under 3.8 s.
Speed Index: 14.2 s
14.2 sVisually, the page fills in at 14.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 659 ms
659 msScripts block taps and scrolling for 659 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 302 ms to 418 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 931 ms
931 msReal visitors wait 931 ms for your server to start answering (75th percentile). Good is under 800 ms.
7 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 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: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 7.7 MB in 497 requests
7.7 MBYour homepage downloads 7.7 MB in 497 requests on a phone: scripts 3.6 MB (195), images 2.4 MB (45) and other files 1.1 MB (227). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (30 KiB) is 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.
3 images below the first screen load straight away
3 images further down the page (121 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.18 g of CO₂e: 262.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “FRAME | Modern Luxury Fashion”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'L', ..." "logo": Liquid err"... is not va)”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
One H1 headline
Your <h1> is empty.
194 internal links, 5 external
The homepage links to 194 pages on frame-store.com and 5 external pages.
4 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “FRAME is a modern luxury fashion brand that blends California ease with Paris sophistication, grounded in quality and c…”.
Canonical URL set
The canonical URL is https://frame-store.com/.
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://frame-store.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 (791 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://frame-store.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://frame-store.com/pages/returns, https://frame-store.com/pages/the-holiday-edit, https://frame-store.com/collections/amelia-gray-x-frame, https://frame-store.com/collections/the-party-dressing-edit, https://frame-store.com/collections/the-corduroy-edit and https://frame-store.com/pages/frame-ritz-paris have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://frame-store.com/collections/the-tailored-edit, whose canonical is https://frame-store.com/collections/the-trouser-edit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://frame-store.com/collections/most-wanted-women, https://frame-store.com/collections/most-wanted-men, https://frame-store.com/collections/new-women, https://frame-store.com/pages/the-holiday-edit, https://frame-store.com/collections/new-men and https://frame-store.com/collections/women and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://i.liadm.com/s/89602?shd_id=XMXkXW0r5E7oDsrlZWam&account_id=frame-denim.myshopify.com.
31 small tap targets
31 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.
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 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.
About 374 words of copy
The homepage carries about 374 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 Women” and “Shop Men”.
18 calls to action
The homepage has 18 calls to action, for example “Shop Women”, “Shop Men” and “Shop Now”.
223 short forms
223 short forms (1 field at most) are right on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
56 cookies set on arrival
56Opening the homepage sets 56 cookies (measured from a US location before any click).
62 other companies contacted
Loading the homepage contacts 62 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 frame-store.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Elevar Conversion Tracking · Okendo · Attentive · Rakuten Affiliate Tracking · Inveterate · Unveild Frame · Checkmate · Kleep X Frame Prod · Swym Wishlist Plus · Polar Analytics · cloudfront.net · attn.tv · global-e.com · frame-store.com · amazonaws.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
- Los Angeles
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 frame-store.com, including 18 speed issues, 5 SEO issues and 3 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.