Website review, no card needed
frederica.com website review
Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 84 checks
This review found 40 issues worth fixing on frederica.com, 15 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
81B- #40,347 of 119,996 reviewed websitesbeats 61%
- #26,886 of 68,004 online storesbeats 54%
- #25,927 of 61,979 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.4 s |
| May 30, 2026 | 5.3 s |
| Jun 6, 2026 | 5.2 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.4 s |
| Jun 27, 2026 | 5.5 s |
| Jul 4, 2026 | 5.7 s |
| Jul 11, 2026 | 5.9 s |
| Jul 18, 2026 | 6.0 s |
| Jul 25, 2026 | 6.1 s |
| Aug 1, 2026 | 5.8 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.2 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.4 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.6 s |
| Oct 17, 2026 | 5.6 s |
| Oct 24, 2026 | 5.6 s |
| Oct 31, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 174 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 189 ms |
| Jun 27, 2026 | 197 ms |
| Jul 4, 2026 | 207 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 214 ms |
| Jul 25, 2026 | 217 ms |
| Aug 1, 2026 | 209 ms |
| Aug 8, 2026 | 208 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 206 ms |
| Sep 19, 2026 | 207 ms |
| Sep 26, 2026 | 217 ms |
| Oct 3, 2026 | 225 ms |
| Oct 10, 2026 | 237 ms |
| Oct 17, 2026 | 246 ms |
| Oct 24, 2026 | 253 ms |
| Oct 31, 2026 | 261 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
Speed
Reduce unused JavaScript
3.1 s · 596 KiBAbout 596 KiB 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.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.1 s
A phone's processor spends 9.1 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and alia-prod.com and others), adding 1.9 MB and 1.0 s of main-thread time.
Shopify adds 411 ms
411 msShopify costs a phone 411 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.
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 274 ms. During a long task the page ignores taps.
2,713 HTML elements
The page has 2,713 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
230 KiB12 files are served with short cache lifetimes, so returning visitors download them again (230 KiB).
Reduce unused CSS
150 ms · 41 KiBAbout 41 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.
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
Legacy JavaScript
54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need.
Improve image delivery
52 KiB4 images could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 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: 20.2 s
20.2 sYour largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 932 ms
932 msScripts block taps and scrolling for 932 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 49% slower for real visitors
+49%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 174 ms to 261 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.4 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 374 requests
4.4 MBYour homepage downloads 4.4 MB in 374 requests on a phone: scripts 1.7 MB (115), other files 1.0 MB (143) and images 958 KiB (79). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
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 (27 elements)
All page content should be contained by landmarks: 27 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)
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 119 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (21 characters)
Your title is only 21 characters: “FREDERICA – Frederica”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
149 internal links, 5 external
The homepage links to 149 pages on frederica.com and 5 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Frederica is a brand that celebrates the perfect balance between taking care of your body and enjoying life. Discover o…”.
Canonical URL set
The canonical URL is https://frederica.com/en-wl.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://frederica.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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,274 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://frederica.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://frederica.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
2 linked pages hidden from search
https://frederica.com/en-wl/collections/all and https://frederica.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages share 2 titles
https://frederica.com/en-wl/products/sunscreen-stick and https://frederica.com/en-wl/collections/frontpage/products/sunscreen-stick all use the title “Sunscreen Color Stick SPF 50+ – Frederica”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://frederica.com/en-wl/collections/all, https://frederica.com/customer_authentication/redirect, https://frederica.com/en-wl/pages/shop-by-benefits, https://frederica.com/en-wl/collections/supplementation, https://frederica.com/en-wl/collections/cosmetics and https://frederica.com/en-wl/collections/packs and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://frederica.com/en-wl/products/sunscreen-stick and https://frederica.com/en-wl/collections/frontpage/products/sunscreen-stick use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://frederica.com/en-wl/collections/frontpage/products/brownie-hair-gummies, whose canonical is https://frederica.com/en-wl/products/brownie-hair-gummies. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://frederica.com/customer_authentication/redirect, https://frederica.com/en-wl/products/sunscreen-stick, https://frederica.com/en-wl/collections/frontpage/products/sunscreen-stick and https://frederica.com/en-wl/collections/frontpage/products/hair-up-gummies have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://frederica.com/en-wl/products/sunscreen-stick and https://frederica.com/en-wl/collections/frontpage/products/sunscreen-stick 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
16 small tap targets
16 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'classList')”.
1 checks passed
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 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 1,198 words of copy
The homepage carries about 1,198 words of visible text.
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “SHOP”, “JOIN US” and “Complaints Book”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 112 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
43 other companies contacted
Loading the homepage contacts 43 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 frederica.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
T Lab Ai Translate · Selecty · Judge Me Reviews · Klaviyo Email Marketing Sms · Kaching Bundles · Sami B2b Lock · Smart Filter Search · Triplewhale · Microsoft Clarity · Uppromote Affiliate · Smart Product Filters · Wholesale Lock Hide Price · Affliate By Secomapp · Madgic Checkout Validation · Freegifts · Grouptify Combined Listings · Upcart · bogos.io
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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
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 frederica.com, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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.