Website review, no card needed
masglo.global website review
Visit site (opens in a new tab)Reviewed 11 November 202640 issues · 88 checks
This review found 40 issues worth fixing on masglo.global, 9 of them high impact, across 88 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
75C- #77,484 of 117,615 reviewed websitesbeats 30%
- #49,603 of 66,923 online storesbeats 22%
- #46,889 of 61,018 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 103 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 100 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 102 ms |
| Aug 15, 2026 | 100 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 101 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 94 ms |
| Oct 24, 2026 | 93 ms |
| Oct 31, 2026 | 89 ms |
| Nov 7, 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
Speed
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 1.8 MB and 1.5 s of main-thread time.
YouTube adds 969 ms
969 msYouTube costs a phone 969 ms of main-thread work and 1.0 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: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
746 KiBAbout 746 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Google Tag Manager adds 361 ms
361 msGoogle Tag Manager costs a phone 361 ms of main-thread work and 292 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 322 ms. During a long task the page ignores taps.
Improve image delivery
313 KiB5 images could be 313 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 61 ms
61 msShopify costs a phone 61 ms of main-thread work and 397 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 CSS
126 KiBAbout 126 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
18 KiB3 files are served with short cache lifetimes, so returning visitors download them again (18 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.
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: 6 ms
6 msYour server sent the HTML in 6 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: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
Total Blocking Time: 896 ms
896 msScripts block taps and scrolling for 896 ms in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Somos una marca multinacional de esmaltes, reconocidos por …”.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 98 ms
98 msReal visitors wait 98 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 796 ms
796 msReal visitors wait 796 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 91 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 177 requests
3.1 MBYour homepage downloads 3.1 MB in 177 requests on a phone: scripts 1.5 MB (45), other files 624 KiB (60) and images 539 KiB (31). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
262 KiB1 image is downloaded at several times the size a phone draws it, for example 5ccf860b9639c41ae078624a_wave-black-on-white-01_-_copia.gif at 3,924 px wide, shown at 360 px. Resized copies would save about 262 KiB.
1 image in older formats
1 image (283 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.
1 image below the first screen load straight away
1 image further down the page (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 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 short (13 characters)
Your title is only 13 characters: “Masglo Global”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 (13 characters)
Your meta description is only 13 characters: “Masglo Global”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
10 links with vague text
10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
51 internal links, 11 external
The homepage links to 51 pages on masglo.global and 11 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Masglo Global”.
Canonical URL set
The canonical URL is https://masglo.global/.
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://masglo.global/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.
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 (244 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://masglo.global/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages share a meta description
https://masglo.global/pages/carta-color, https://masglo.global/pages/contact, https://masglo.global/pages/encuentra-tu-distribuidor, https://masglo.global/blogs/articulos, https://masglo.global/collections/esmaltes-de-unas-tradicionales and https://masglo.global/collections/bases-unas-tradicionales and 9 others use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://masglo.global/pages/carta-color, https://masglo.global/blogs/articulos and https://masglo.global/blogs/tendencias/unas-mantequilla have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://masglo.global/pages/carta-color, https://masglo.global/pages/contact and https://masglo.global/collections/clinical 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 25 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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
16 of 19 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.
Only about 206 words
The homepage has only about 206 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Subscribe”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
15 other companies contacted
Loading the homepage contacts 15 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 masglo.global, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder
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 masglo.global, including 16 speed issues, 5 SEO issues and 3 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.