Website review, no card needed
froyaorganics.com website review
Visit site (opens in a new tab)Reviewed 5 November 202641 issues · 90 checks
This review found 41 issues worth fixing on froyaorganics.com, 15 of them high impact, across 90 checks. The most urgent: main-thread work: 11.1 s. 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
76C- #75,296 of 124,051 reviewed websitesbeats 35%
- #48,233 of 69,761 online storesbeats 26%
- #45,685 of 63,448 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 190 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 190 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 222 ms |
| Jul 4, 2026 | 230 ms |
| Jul 11, 2026 | 235 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 232 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 229 ms |
| Aug 15, 2026 | 232 ms |
| Aug 22, 2026 | 238 ms |
| Aug 29, 2026 | 241 ms |
| Sep 5, 2026 | 243 ms |
| Sep 12, 2026 | 244 ms |
| Sep 19, 2026 | 242 ms |
| Sep 26, 2026 | 246 ms |
| Oct 3, 2026 | 252 ms |
| Oct 10, 2026 | 257 ms |
| Oct 17, 2026 | 263 ms |
| Oct 24, 2026 | 265 ms |
| Oct 31, 2026 | 264 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
1.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.6 s
10.9 s
Speed
Main-thread work: 11.1 s
A phone's processor spends 11.1 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,135 HTML elements
The page has 6,135 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 (loox.io, Facebook and runconverge.com and others), adding 1.2 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
800 KiBAbout 800 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
675 KiB23 files are served with short cache lifetimes, so returning visitors download them again (675 KiB).
Reduce unused CSS
450 ms · 116 KiBAbout 116 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 543 ms. During a long task the page ignores taps.
loox.io adds 523 ms
523 msloox.io costs a phone 523 ms of main-thread work and 28 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 404 ms
404 msFacebook costs a phone 404 ms of main-thread work and 302 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.
runconverge.com adds 279 ms
279 msrunconverge.com costs a phone 279 ms of main-thread work and 248 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.
Klaviyo adds 209 ms
209 msKlaviyo costs a phone 209 ms of main-thread work and 319 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
150 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
139 KiB13 images could be 139 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.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 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: 24.8 s
24.8 sThe page becomes fully interactive after 24.8 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 246 ms
246 msReal visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 190 ms to 264 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 959 ms
959 msReal visitors wait 959 ms for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (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 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 361 requests
5.8 MBYour homepage downloads 5.8 MB in 361 requests on a phone: scripts 2.0 MB (112), media 1.4 MB (1) and images 834 KiB (72). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
19 KiB1 image is downloaded at several times the size a phone draws it, for example IMG_1_8c681b46-2a29-4394-8f0b-a4d7759e9a48.jpg at 389 px wide, shown at 106 px. Resized copies would save about 19 KiB.
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 198.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
49 text elements with low contrast
49 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
27 tap targets too small
27 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
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.
39 links without text
39 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
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.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
360 internal links, 5 external
The homepage links to 360 pages on froyaorganics.com and 5 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Shop natural skincare & haircare for mature skin and thinning hair. Wild Arctic plant balms with visible results in 60 …”.
One H1 headline
Your main headline reads: “Skincare That Finally Understands Mature Skin”.
Title: 51 characters
Your title is a healthy 51 characters: “Natural Skincare & Haircare from Wild Arctic Plants”.
Canonical URL set
The canonical URL is https://froyaorganics.com/.
Structured data in place
Structured data found: ItemList, 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://froyaorganics.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (10,238 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://froyaorganics.com/llms.txt (6 KiB, 48 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a title
https://froyaorganics.com/a/loop_subscriptions/get-subscription-link and https://froyaorganics.com/customer_authentication/redirect have no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://froyaorganics.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://froyaorganics.com/a/loop_subscriptions/get-subscription-link and https://froyaorganics.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://froyaorganics.com/pages/guarantee, https://froyaorganics.com/pages/our-saga and https://froyaorganics.com/pages/affiliate-program use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://froyaorganics.com/pages/affiliate-program, https://froyaorganics.com/a/loop_subscriptions/get-subscription-link and https://froyaorganics.com/customer_authentication/redirect 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 51 found) and read each the way a search engine does.
3 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.
Best practices
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187259252&Ver=2&mid=6330a80a-586e-47fb-bf9f-6444ecf6c3b0&bo=1&sid=37f6a990d8b011f18f036f0717735b99&vid=37f6ce50d8b011f1ba58c1b249c20fca&vids=1&msclkid=N&pi=918639831&l.
41 small tap targets
41 of 181 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 5,548 words of copy
The homepage carries about 5,548 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL PRODUCTS”.
71 calls to action
The homepage has 71 calls to action, for example “Shop all products”, “SHOP ALL” and “Shop”.
33 short forms
33 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1,207 testimonial or review blocks, 24 customer or partner logos, a star rating and “922,388+ happy customers”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 5 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.
50 cookies set on arrival
50Opening the homepage sets 50 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.
70 other companies contacted
Loading the homepage contacts 70 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 froyaorganics.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · P7p987m69 Opensend · Klaviyo Email Marketing Sms · Redo · Microsoft Clarity · Gdpr Backpack · Applovin Shop Integration · Aftersell · loox.io · socialsnowball.io · convertflow.co · cognitionhub.no · getangler.ai · cloudfront.net
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
- The footer still says © 2025.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on froyaorganics.com, including 22 speed issues, 1 SEO issue 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.