Website review, no card needed

massollo.com logo

massollo.com website review

Visit site (opens in a new tab)Reviewed 16 November 202625 issues · 71 checks

This review found 25 issues worth fixing on massollo.com, 6 of them high impact, across 71 checks. The most urgent: 1 linked page is broken. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of massollo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. massollo.com at 0.4 s0.4 s
  2. massollo.com at 0.8 s0.8 s
  3. massollo.com at 1.1 s1.1 s
  4. massollo.com at 1.5 s1.5 s
  5. massollo.com at 1.9 s1.9 s
  6. massollo.com at 2.3 s2.3 s
  7. massollo.com at 2.6 s2.6 s
  8. massollo.com at 3.0 s3.0 s

Speed

4 to fix100
  • Render-blocking requests

    550 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Improve image delivery

    421 KiB

    10 images could be 421 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    318 KiB

    31 files are served with short cache lifetimes, so returning visitors download them again (318 KiB).

  • Shopify adds 10 ms

    10 ms

    Shopify costs a phone 10 ms of main-thread work and 848 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.

  • Reduce unused JavaScript

    237 KiB

    About 237 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    150 ms · 31 KiB

    About 31 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Klaviyo, Cloudflare and Shopify and others), adding 940 KiB and 85 ms of main-thread time.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 88 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    29 KiB

    Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

  • 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.

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 406 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100
  • Time to Interactive: 4.5 s

    4.5 s

    The page becomes fully interactive after 4.5 s. Good is under 3.8 s.

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

5 checks passed
  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “"La nature nous inspire à nous ouvrir au monde, à travers d…”.

  • Total Blocking Time: 58 ms

    58 ms

    Scripts block the page for only 58 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix55
  • 4 images far larger than shown

    899 KiB

    4 images are downloaded at several times the size a phone draws them, for example brassiere-couleur-marron-sport-yoga-fitness-casual-femme-mas at 1,080 px wide, shown at 135 px. Resized copies would save about 899 KiB.

  • Page weight: 2.1 MB in 81 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 81 requests on a phone: other files 933 KiB (23), images 638 KiB (16) and scripts 462 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.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.

  • About 0.6 g of CO₂ per visit

    0.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 70.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8994
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 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.

2 checks passed
  • Every image has alt text

    All 14 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • Meta description is long (220 characters)

    Your meta description is 220 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.

  • 48 internal links, 0 external

    The homepage links to 48 pages on massollo.com and 0 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Massollo”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Massollo | Vêtements de sport et loisirs inspirés du wax”.

  • Canonical URL set

    The canonical URL is https://massollo.com/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://massollo.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://massollo.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

2 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (560 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://massollo.com/collections/liquidation, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 7 pages share 2 titles

    https://massollo.com/collections/liquidation/products/brassiere-safari, https://massollo.com/collections/liquidation/products/brassiere-safari-black and https://massollo.com/collections/liquidation/products/brassiere-heritage-black all use the title “Brassière femme sport et yoga imprimée wax orange - Crop Top – Massol…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages share a meta description

    https://massollo.com/collections/liquidation/products/brassiere-safari, https://massollo.com/collections/liquidation/products/brassiere-safari-black and https://massollo.com/collections/liquidation/products/brassiere-heritage-black use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Error: <path> attribute d: Expected number, "…812 2.092t14.946q1.165 0 1.977-.…".”.

2 checks passed
  • Tap targets are thumb-sized

    30 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 441 words of copy

    The homepage carries about 441 words of visible text.

2 checks passed
  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before 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.

  • 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 massollo.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · backinstock.org

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

  • The footer still says © 2025.

Stack

E-commerce
Shopify
Hosting
Cloudflare

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 massollo.com, including 6 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25