Website review, no card needed
maryling.com website review
Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 78 checks
This review found 31 issues worth fixing on maryling.com, 10 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
83B- #26,485 of 114,596 reviewed websitesbeats 72%
- #17,738 of 66,250 online storesbeats 67%
- #17,220 of 60,622 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 174 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 167 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 186 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 86 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 65 ms |
| Oct 3, 2026 | 55 ms |
| Oct 10, 2026 | 60 ms |
| Oct 17, 2026 | 70 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 80 ms |
| Nov 7, 2026 | 87 ms |
| Nov 14, 2026 | 91 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.8 s
1.6 s
2.4 s
3.3 s
4.1 s
4.9 s
5.7 s
6.5 s
Speed
Reduce unused JavaScript
2.2 s · 542 KiBAbout 542 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 394 KiB14 files are served with short cache lifetimes, so returning visitors download them again (394 KiB).
Mobile performance score: 61
61/100Your mobile performance score is 61. 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 (Shopify, Google CDN and cloudfront.net and others), adding 1.6 MB and 503 ms of main-thread time.
Legacy JavaScript
500 ms · 74 KiBPolyfills for old browsers add 74 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 142 ms
142 msShopify costs a phone 142 ms of main-thread work and 392 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.
cloudfront.net adds 97 ms
97 mscloudfront.net costs a phone 97 ms of main-thread work and 410 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.
Google CDN adds 104 ms
104 msGoogle CDN costs a phone 104 ms of main-thread work and 299 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.
Improve image delivery
200 ms · 192 KiB8 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
260 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 15.0 s
15.0 sThe page becomes fully interactive after 15.0 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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 INP: 91 ms
91 msReal visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 358 ms
358 msReal visitors wait 358 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 118 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 90 ms
90 msScripts block the page for only 90 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 286 requests
3.3 MBYour homepage downloads 3.3 MB in 286 requests on a phone: scripts 1.5 MB (131), other files 673 KiB (111) and images 651 KiB (17). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (87 KiB) is 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.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
autocomplete attribute must be used correctly (1 element)
autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate 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.
2 checks passed
Every image has alt text
All 21 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 short (55 characters)
Your meta description is only 55 characters: “Discover Timeless Designs,Awaken Your Inner Confidence.”. 70 to 160 characters is enough to sell the click.
66 internal links, 7 external
The homepage links to 66 pages on maryling.com and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “MARYLING”.
Title: 52 characters
Your title is a healthy 52 characters: “MARYLING Official Site | Interpreting Luxury Fashion”.
Canonical URL set
The canonical URL is https://www.maryling.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.maryling.com/sitemap.xml.
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.
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.
llms.txt published
The site publishes https://www.maryling.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://www.maryling.com/collections/new-arrivals, https://www.maryling.com/collections/best-selling, https://www.maryling.com/collections/dresses, https://www.maryling.com/collections/blazers, https://www.maryling.com/collections/jackets-coats and https://www.maryling.com/collections/jumpsuits and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.maryling.com/collections/new-arrivals, https://www.maryling.com/collections/best-selling, https://www.maryling.com/collections/dresses, https://www.maryling.com/collections/blazers, https://www.maryling.com/collections/jackets-coats and https://www.maryling.com/collections/jumpsuits and 9 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 37 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
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “merchantWidgetScript.addEventListener is not a function”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
15 of 16 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 136 words
The homepage has only about 136 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Information” and “icon-email Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
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 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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 2 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.
32 other companies contacted
Loading the homepage contacts 32 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 maryling.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Stream Email Sms · Google Youtube · Airwallex Fraud Protection · amazonaws.com · cloudfront.net
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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on maryling.com, including 13 speed issues, 2 SEO issues and 5 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.