Website review, no card needed
fortuspilates.ca website review
Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 63 checks
This review found 25 issues worth fixing on fortuspilates.ca, 7 of them high impact, across 63 checks. The most urgent: page weight: 62.9 MB in 296 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
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
Reduce unused JavaScript
2.7 s · 443 KiBAbout 443 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Improve image delivery
5.4 MB33 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
700 ms · 218 KiB18 files are served with short cache lifetimes, so returning visitors download them again (218 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and rebuyengine.com and others), adding 1.5 MB and 741 ms of main-thread time.
Shopify adds 211 ms
211 msShopify costs a phone 211 ms of main-thread work and 750 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.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,839 HTML elements
The page has 1,839 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
rebuyengine.com adds 135 ms
135 msrebuyengine.com costs a phone 135 ms of main-thread work and 300 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.
Render-blocking requests
250 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Legacy JavaScript
200 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.
Reduce unused CSS
140 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
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
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: 32.3 s
32.3 sYour largest element takes 32.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 34.0 s
34.0 sThe page becomes fully interactive after 34.0 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 333 ms
333 msScripts block taps and scrolling for 333 ms in total while the page loads. Good is under 200 ms.
5 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 108 ms
108 msReal visitors wait 108 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 622 ms
622 msReal visitors wait 622 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.097
0.097The layout barely moves while loading (CLS 0.097, good is under 0.1).
Images and page weight
Page weight: 62.9 MB in 296 requests
62.9 MBYour homepage downloads 62.9 MB in 296 requests on a phone: media 53.4 MB (5), images 6.6 MB (47) and scripts 1.2 MB (94). Under 2 MB keeps phones on slow connections fast.
About 17.8 g of CO₂ per visit
17.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 17.82 g of CO₂e: 2138.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 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.
SEO
No XML sitemap
No XML sitemap at https://fortuspilates.ca/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at fortuspilates.ca/robots.txt, the first file search crawlers ask for.
One H1 headline
Your <h1> is empty.
65 internal links, 7 external
The homepage links to 65 pages on fortuspilates.ca and 7 external pages.
5 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Experience Pilates perfection with our studio quality reformers. High quality reformers for studio and home. Precision …”.
Title: 46 characters
Your title is a healthy 46 characters: “Fortus Pilates - Reformers for Studio and Home”.
Canonical URL set
The canonical URL is https://fortuspilates.ca/en-us.
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.
AI search readiness
1 checks passed
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.
Other pages
6 pages without a meta description
https://fortuspilates.ca/en-us/pages/instructor-training-bundle, https://fortuspilates.ca/en-us/pages/studio-partner-program, https://fortuspilates.ca/en-us/pages/studios, https://fortuspilates.ca/en-us/pages/customer-success-stories, https://fortuspilates.ca/en-us/pages/financing-for-home-users and https://fortuspilates.ca/en-us/pages/try-before-you-buy have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
8 console errors
8 errors were logged to the browser console during Google's test (“%c09:55:27.392 PST %cPixel SDK %cERROR %cError waiting for Shopify color: gray color: magenta; font…”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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,084 words of copy
The homepage carries about 1,084 words of visible text.
5 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop”, “Try Before You Buy” and “Contact”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 115 testimonial or review blocks and 6 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 fortuspilates.ca, 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
Common Ninja Comparison Tables · Weglot Translate Your Store · Warnify Pro Warnings · Judge Me Reviews · Pagefly Ai Page Builder · Product Warnings · Yanet Faq Page Product Faqs · Dealeasy · Countdown Timer · Hidepay · commoninja.com · chimpstatic.com · rebuyengine.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on fortuspilates.ca, including 16 speed issues and 3 SEO issues. 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.