Website review, no card needed
fora-shop.com website review
Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 77 checks
This review found 26 issues worth fixing on fora-shop.com, 7 of them high impact, across 77 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
84B- #21,736 of 121,427 reviewed websitesbeats 77%
- #14,085 of 68,698 online storesbeats 73%
- #13,666 of 62,600 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 94 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 133 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 103 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 110 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 111 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 120 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.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Reduce unused JavaScript
1.7 s · 469 KiBAbout 469 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Use efficient cache lifetimes
750 ms · 381 KiB17 files are served with short cache lifetimes, so returning visitors download them again (381 KiB).
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Accessibe Accessibility Overlay, Shopify and reamaze.com and others), adding 1.3 MB and 590 ms of main-thread time.
Render-blocking requests
300 ms15 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 160 ms
160 msShopify costs a phone 160 ms of main-thread work and 453 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 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.
Improve image delivery
19 KiB2 images could be 19 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Promotional banner showing a man smiling while using a FORA…”.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 94 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 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 INP: 120 ms
120 msReal visitors wait 120 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 574 ms
574 msReal visitors wait 574 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 163 ms
163 msScripts block the page for only 163 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.9 MB in 351 requests
2.9 MBYour homepage downloads 2.9 MB in 351 requests on a phone: scripts 1.4 MB (120), other files 1.1 MB (187) and images 213 KiB (11). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
fora-p80-wireless-bluetooth-blood-pressure-monitor.png 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 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.7 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
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
2 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.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
47 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: 47 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.fora-shop.com/cdn/shop/files/FORA_logo_250X250_7e…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
42 internal links, 7 external
The homepage links to 42 pages on fora-shop.com and 7 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Shop accurate and reliable home health products at ForaCare. Find blood glucose, ketone, cholesterol testing kits, bloo…”.
One H1 headline
Your main headline reads: “ForaCare Inc.”.
Title: 60 characters
Your title is a healthy 60 characters: “ForaCare Inc. | Your Source for Quality Home Health Products”.
Canonical URL set
The canonical URL is https://www.fora-shop.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://www.fora-shop.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 (420 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fora-shop.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.fora-shop.com/collections/all and https://www.fora-shop.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.fora-shop.com/products/fora-test-ngo-advance-ketone-kit-standard, whose canonical is https://www.fora-shop.com/products/fora-test-ngo-advance-ketone-kit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
9 pages without an H1
https://www.fora-shop.com/collections/all, https://www.fora-shop.com/collections/fora-online-store-special-offers, https://www.fora-shop.com/pages/fora-rewards-program, https://www.fora-shop.com/collections/blood-glucose-monitoring-kits-meters-test-strips, https://www.fora-shop.com/collections/ketone-cholesterol-lactate-testing-strips-kits and https://www.fora-shop.com/collections/home-health-devices-blood-pressure-scales-thermometers-more and 3 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 24 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “SyntaxError: Failed to execute 'closest' on 'Element': '[id*="acsb"], .acsb, #acsb, [data-acsb], [data-acsb-*]' is not …”.
2 checks passed
Tap targets are thumb-sized
24 of 25 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 358 words of copy
The homepage carries about 358 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 Ketone Kit!” and “Learn More!”.
10 calls to action
The homepage has 10 calls to action, for example “Subscribe & Save”, “Shop Ketone Kit!” and “Learn More!”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is 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 Meta Pixel (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (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.
32 other companies contacted
Loading the homepage contacts 32 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 fora-shop.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Searchpie Seo Speed · Judge Me Reviews · Smart Filter Search · Reamaze Live Chat Helpdesk · Pagefly Ai Page Builder · Smart Product Filters · Pushowl · Gdpr Backpack · Omnisend · Bestpush · automizely.com · smile.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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on fora-shop.com, including 11 speed issues, 2 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.