Website review, no card needed
mainstreetmassage.ca website review
Visit site (opens in a new tab)Reviewed 9 November 202643 issues · 83 checks
This review found 43 issues worth fixing on mainstreetmassage.ca, 14 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
72C- #97,745 of 126,442 reviewed websitesbeats 20%
- #59,778 of 70,471 online storesbeats 12%
- #55,592 of 63,972 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
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.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Improve image delivery
27.4 s · 11.4 MB59 images could be 11.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 27.4 s faster on a phone.
5,117 HTML elements
The page has 5,117 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 third-party services on the page
4 third-party services load with your homepage (Cloudflare, cloudfront.net and plcl.me and others), adding 11.0 MB and 50 ms of main-thread time.
Use efficient cache lifetimes
950 ms · 202 KiB14 files are served with short cache lifetimes, so returning visitors download them again (202 KiB).
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 10.7 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.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 166 KiBAbout 166 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
800 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 700 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 46 KiBAbout 46 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.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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: 19 ms
19 msYour server sent the HTML in 19 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: 33.6 s
33.6 sYour largest element takes 33.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Popup Banner”.
Time to Interactive: 33.9 s
33.9 sThe page becomes fully interactive after 33.9 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 284 ms
284 msScripts block taps and scrolling for 284 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
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: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 12.5 MB in 139 requests
12.5 MBYour homepage downloads 12.5 MB in 139 requests on a phone: images 12.1 MB (121), scripts 285 KiB (8) and stylesheets 73 KiB (5). Under 2 MB keeps phones on slow connections fast.
35 images far larger than shown
6.6 MB35 images are downloaded at several times the size a phone draws them, for example id_cbd_de6693eb-c6ee-4da7-863f-c08794377781_1780407107663.pn at 1,920 px wide, shown at 390 px. Resized copies would save about 6.6 MB.
4 images over 500 KB
4 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
30 images in older formats
30 images (10.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
An image on the first screen is lazy-loaded
DesktopID-1864-20260502144747.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 3.6 g of CO₂ per visit
3.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.56 g of CO₂e: 426.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 593 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “JUARASLOT88: Server Slot Gacor Jackpot WD Jutaan Slot88 Maxwin Scatter Hari Ini”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (165 characters)
Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://ordercharliesrestaurant.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at ordercharliesrestaurant.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
400 internal links, 25 external
The homepage links to 400 pages on mainstreetmassage.ca and 25 external pages.
2 checks passed
One H1 headline
Your main headline reads: “JUARASLOT88: Server Slot Gacor Jackpot WD Jutaan Slot88 Maxwin Scatter Hari Ini”.
Canonical URL set
The canonical URL is https://ordercharliesrestaurant.com/.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://ordercharliesrestaurant.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,074 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages point its canonical at the homepage
https://ordercharliesrestaurant.com/contact-us, https://ordercharliesrestaurant.com/desktop/hot-games, https://ordercharliesrestaurant.com/desktop/slots/pragmatic, https://ordercharliesrestaurant.com/special, https://ordercharliesrestaurant.com/desktop/slots/jili and https://ordercharliesrestaurant.com/desktop/slots/habanero and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
16 pages share a title
/, https://ordercharliesrestaurant.com/contact-us, https://ordercharliesrestaurant.com/desktop/hot-games, https://ordercharliesrestaurant.com/desktop/slots/pragmatic, https://ordercharliesrestaurant.com/special and https://ordercharliesrestaurant.com/desktop/slots/jili and 10 others all use the title “JUARASLOT88: Server Slot Gacor Jackpot WD Jutaan Slot88 Maxwin Scatte…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages share a meta description
https://ordercharliesrestaurant.com/contact-us, https://ordercharliesrestaurant.com/desktop/hot-games, https://ordercharliesrestaurant.com/desktop/slots/pragmatic, https://ordercharliesrestaurant.com/special, https://ordercharliesrestaurant.com/desktop/slots/jili and https://ordercharliesrestaurant.com/desktop/slots/habanero and 9 others use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://ordercharliesrestaurant.com/special has 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 87 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
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 'childElementCount')”.
7 distorted images
7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
227 of 245 tappable elements near the top are at least 24 px.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 785 words of copy
The homepage carries about 785 words of visible text.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 mainstreetmassage.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on mainstreetmassage.ca, including 17 speed issues, 6 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.