Website review, no card needed
maysama.co website review
Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 71 checks
This review found 26 issues worth fixing on maysama.co, 10 of them high impact, across 71 checks. The most urgent: render-blocking 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
Site score
79C- #55,965 of 125,585 reviewed websitesbeats 50%
- #36,609 of 70,212 online storesbeats 42%
- #35,056 of 63,785 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.5 s |
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.8 s |
| Jun 6, 2026 | 6.0 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.3 s |
| Jun 27, 2026 | 6.6 s |
| Jul 4, 2026 | 6.7 s |
| Jul 11, 2026 | 7.8 s |
| Jul 18, 2026 | 8.0 s |
| Jul 25, 2026 | 7.5 s |
| Aug 1, 2026 | 7.5 s |
| Aug 8, 2026 | 7.0 s |
| Aug 15, 2026 | 6.8 s |
| Aug 22, 2026 | 7.0 s |
| Aug 29, 2026 | 6.6 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.3 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 5.1 s |
| Oct 3, 2026 | 5.3 s |
| Oct 10, 2026 | 5.7 s |
| Oct 17, 2026 | 6.1 s |
| Oct 24, 2026 | 6.4 s |
| Oct 31, 2026 | 6.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 150 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 159 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 166 ms |
| Aug 1, 2026 | 172 ms |
| Aug 8, 2026 | 185 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 202 ms |
| Aug 29, 2026 | 198 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 167 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 175 ms |
| Oct 31, 2026 | 198 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
Speed
Render-blocking requests
2.5 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. 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 (Google Tag Manager, Shopify and cookiefirst.com and others), adding 1.4 MB and 558 ms of main-thread time.
Reduce unused JavaScript
450 ms · 213 KiBAbout 213 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 556 ms
556 msGoogle Tag Manager costs a phone 556 ms of main-thread work and 688 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.
Shopify adds 2 ms
2 msShopify costs a phone 2 ms of main-thread work and 652 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Improve image delivery
77 KiB3 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
35 KiB7 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 535 ms of it running JavaScript. That is comfortably low.
Server response: 27 ms
27 msYour server sent the HTML in 27 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.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Up to 50% off”. Most of its time is element render delay (2.5 s).
Real-user INP: 221 ms
221 msReal visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 150 ms to 198 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 233 ms
233 msScripts block taps and scrolling for 233 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.5 s to 6.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 667 ms
667 msReal visitors wait 667 ms for your server to start answering (75th percentile). Good is under 800 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.4 MB in 116 requests
2.4 MBYour homepage downloads 2.4 MB in 116 requests on a phone: scripts 1.6 MB (59), images 392 KiB (12) and HTML 192 KiB (1). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
AURA_LED_Mask.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.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.2 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
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Pulsed LED Therapy Devices and Green Rooibos Skincare | Maysama – Maysama UK”.
2 H1 headlines
There are 2 <h1> headlines (“POWERED BY PULSE. GROUNDED IN NATURE.” and “”). One clear main headline is easier for people and search engines.
83 internal links, 20 external
The homepage links to 83 pages on maysama.co and 20 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Redefining the at-home skin care with advanced pulsed LED therapy solutions paired with synergistic, award-winning gree…”.
Canonical URL set
The canonical URL is https://maysama.co/.
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://maysama.co/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (973 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://maysama.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://maysama.co/collections/all, https://maysama.co/policies/shipping-policy, https://maysama.co/pages/how-it-works, https://maysama.co/blogs/news and https://maysama.co/pages/before-afters have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://maysama.co/collections/all, https://maysama.co/pages/intelligent-micro-pulsing-technology, https://maysama.co/pages/pulsed-led-light-therapy, https://maysama.co/pages/how-it-works, https://maysama.co/pages/about and https://maysama.co/pages/before-afters and 2 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 36 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.
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.
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 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
19 of 20 tappable elements near the top are at least 24 px.
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 544 words of copy
The homepage carries about 544 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE SALE”.
3 calls to action
The homepage has 3 calls to action, for example “Shop”, “Shop the sale” and “Get In Touch”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
16 other companies contacted
Loading the homepage contacts 16 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 maysama.co, 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 22 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Loyalty Rewards And Referrals · Sami B2b Lock · T Lab Ai Translate · Min Max Limits By Limitsify · Okendo · Selecty · Variant Image Wizard Swatch · Variant Title King · Ecomposer Builder · Klaviyo Email Marketing Sms · Triplewhale · Content Translation · Wholesale Lock Hide Price · Frontend · Monk Free Gift With Purchase · Quick Announcement Bar Prod · Forms · Thank You Page · Aod Before After Widget · calconic.com · hextom.com · Hulk Product Options
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 | Google Tag Manager
- 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 maysama.co, including 16 speed issues and 2 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.