Website review, no card needed
montmarte.com website review
Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 86 checks
This review found 40 issues worth fixing on montmarte.com, 9 of them high impact, across 86 checks. The most urgent: fails Core Web Vitals for real visitors. 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
76C- #73,020 of 119,682 reviewed websitesbeats 34%
- #47,042 of 67,864 online storesbeats 26%
- #44,621 of 61,860 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 202 ms |
| May 23, 2026 | 199 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 201 ms |
| Jun 20, 2026 | 201 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 201 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 208 ms |
| Aug 1, 2026 | 206 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 207 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 208 ms |
| Sep 5, 2026 | 210 ms |
| Sep 12, 2026 | 213 ms |
| Sep 19, 2026 | 219 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 234 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 235 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 228 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.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
3,640 HTML elements
The page has 3,640 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
700 ms · 759 KiB25 images could be 759 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, roseperl.com and Facebook and others), adding 1.7 MB and 767 ms of main-thread time.
Use efficient cache lifetimes
300 ms · 643 KiB18 files are served with short cache lifetimes, so returning visitors download them again (643 KiB).
Reduce unused JavaScript
300 ms · 526 KiBAbout 526 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 285 ms
285 msGoogle Tag Manager costs a phone 285 ms of main-thread work and 483 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.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
roseperl.com adds 147 ms
147 msroseperl.com costs a phone 147 ms of main-thread work and 506 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 247 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 83 KiBPolyfills for old browsers add 83 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 74 KiBAbout 74 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.
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: 17 ms
17 msYour server sent the HTML in 17 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.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Background Image Hero”.
Real-user INP: 246 ms
246 msReal visitors wait 246 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 938 ms
938 msReal visitors wait 938 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 501 ms
501 msScripts block taps and scrolling for 501 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 202 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 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.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
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: 4.8 MB in 222 requests
4.8 MBYour homepage downloads 4.8 MB in 222 requests on a phone: scripts 2.2 MB (66), images 1.3 MB (46) and other files 781 KiB (87). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Mont-Marte-Marbling-Art-Set-Header-Banner-1504x928px-mobile_ 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 1.3 g of CO₂ per visit
1.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.35 g of CO₂e: 161.9 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
8 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
80 links with vague text
80 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Title is short (17 characters)
Your title is only 17 characters: “Mont Marte Global”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (17 characters)
Your meta description is only 17 characters: “Mont Marte Global”. 70 to 160 characters is enough to sell the click.
6 H1 headlines
There are 6 <h1> headlines (“Christmasmade creative”, “MarblingArt Set” and “Creative ClayMake Me”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Corporation) but with 1 problem, for example “Corporation: sameAs is an empty list”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
1,063 internal links, 9 external
The homepage links to 1,063 pages on montmarte.com and 9 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.montmarte.com/.
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://www.montmarte.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,683 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.montmarte.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a meta description
https://www.montmarte.com/pages/store-locator, https://www.montmarte.com/pages/contact and https://www.montmarte.com/pages/swym-wishlist use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://www.montmarte.com/pages/swym-wishlist, https://www.montmarte.com/collections/new-arrivals, https://www.montmarte.com/collections/art-paint, https://www.montmarte.com/blogs/tips-techniques/texture-techniques, https://www.montmarte.com/collections/acrylic and https://www.montmarte.com/collections/oil and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.montmarte.com/pages/contact, https://www.montmarte.com/pages/swym-wishlist and https://www.montmarte.com/collections/new-arrivals have 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 199 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
33 of 37 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 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 1,470 words of copy
The homepage carries about 1,470 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Mix & Make Chalk Kits”.
18 calls to action
The homepage has 18 calls to action, for example “Contact”, “Login or register” and “Contact us”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (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.
25 other companies contacted
Loading the homepage contacts 25 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 montmarte.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Powerful Form Builder · addons.business · azureedge.net · roseperl.com · Swym Wishlist Plus
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
- E-commerce
- Shopify
- 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 40 issues on montmarte.com, including 18 speed issues, 6 SEO issues and 2 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.