Website review, no card needed
futuralaboratories.com website review
Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 69 checks
This review found 26 issues worth fixing on futuralaboratories.com, 5 of them high impact, across 69 checks. The most urgent: 1 page without a title. 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
82B- #33,670 of 119,740 reviewed websitesbeats 66%
- #22,430 of 67,889 online storesbeats 60%
- #21,679 of 61,876 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 972 ms |
| May 30, 2026 | 899 ms |
| Jun 6, 2026 | 877 ms |
| Jun 13, 2026 | 893 ms |
| Jun 20, 2026 | 863 ms |
| Jun 27, 2026 | 963 ms |
| Jul 4, 2026 | 971 ms |
| Jul 11, 2026 | 968 ms |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 988 ms |
| Aug 1, 2026 | 966 ms |
| Aug 8, 2026 | 975 ms |
| Aug 15, 2026 | 929 ms |
| Aug 22, 2026 | 950 ms |
| Aug 29, 2026 | 997 ms |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 984 ms |
| Oct 10, 2026 | 915 ms |
| Oct 17, 2026 | 884 ms |
| Oct 24, 2026 | 864 ms |
| Oct 31, 2026 | 865 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 80 ms |
| May 23, 2026 | 72 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 70 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 69 ms |
| Jul 4, 2026 | 68 ms |
| Jul 11, 2026 | 66 ms |
| Jul 18, 2026 | 71 ms |
| Jul 25, 2026 | 64 ms |
| Aug 1, 2026 | 66 ms |
| Aug 8, 2026 | 65 ms |
| Aug 15, 2026 | 63 ms |
| Aug 22, 2026 | 70 ms |
| Aug 29, 2026 | 69 ms |
| Sep 5, 2026 | 69 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 70 ms |
| Sep 26, 2026 | 74 ms |
| Oct 3, 2026 | 75 ms |
| Oct 10, 2026 | 73 ms |
| Oct 17, 2026 | 72 ms |
| Oct 24, 2026 | 73 ms |
| Oct 31, 2026 | 74 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.6 s
3.0 s
Speed
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Signyfyd, Klaviyo and Riskified and others), adding 602 KiB and 833 ms of main-thread time.
Signyfyd adds 714 ms
714 msSignyfyd costs a phone 714 ms of main-thread work and 283 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 281 ms. During a long task the page ignores taps.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 76 KiB2 images could be 76 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Use efficient cache lifetimes
50 ms · 79 KiB14 files are served with short cache lifetimes, so returning visitors download them again (79 KiB).
Minify JavaScript
120 ms · 6 KiB6 KiB could be saved by minifying JavaScript.
Legacy JavaScript
50 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 8.4 s
8.4 sThe page becomes fully interactive after 8.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.161
0.161The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 225 ms
225 msScripts block taps and scrolling for 225 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 80 ms to 74 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Images and page weight
An image on the first screen is lazy-loaded
banner_metrocards.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 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.8 MB in 224 requests
1.8 MBYour homepage downloads 1.8 MB in 224 requests on a phone: other files 833 KiB (113), scripts 602 KiB (71) and images 218 KiB (14). That is a lean page.
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
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 4 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (19 characters)
Your title is only 19 characters: “FUTURA LABORATORIES”. Between 30 and 65 characters leaves room to say what you do and for whom.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
28 internal links, 6 external
The homepage links to 28 pages on futuralaboratories.com and 6 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://futuralaboratories.com/.
Structured data in place
Structured data found: 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://futuralaboratories.com/sitemap.xml.
AI search readiness
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://futuralaboratories.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://futuralaboratories.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://futuralaboratories.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
10 pages without a meta description
https://futuralaboratories.com/collections/apparel, https://futuralaboratories.com/collections/accessories, https://futuralaboratories.com/collections/footwear, https://futuralaboratories.com/collections/home, https://futuralaboratories.com/collections/sale and https://futuralaboratories.com/collections/shop-all and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://futuralaboratories.com/pages/collaboratories, https://futuralaboratories.com/pages/about and https://futuralaboratories.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 12 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
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.
Only about 29 words
The homepage has only about 29 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP”.
3 calls to action
The homepage has 3 calls to action, for example “SHOP”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
13 other companies contacted
Loading the homepage contacts 13 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 futuralaboratories.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on futuralaboratories.com, including 10 speed issues, 4 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.