Website review, no card needed

mashlabs.shop logo

mashlabs.shop website review

Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 79 checks

This review found 29 issues worth fixing on mashlabs.shop, 7 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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 mashlabs.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mashlabs.shop at 0.6 s0.6 s
  2. mashlabs.shop at 1.2 s1.2 s
  3. mashlabs.shop at 1.8 s1.8 s
  4. mashlabs.shop at 2.5 s2.5 s
  5. mashlabs.shop at 3.1 s3.1 s
  6. mashlabs.shop at 3.7 s3.7 s
  7. mashlabs.shop at 4.3 s4.3 s
  8. mashlabs.shop at 4.9 s4.9 s

Speed

6 to fix69
  • Reduce unused JavaScript

    1.4 s · 611 KiB

    About 611 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. 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 CDN, Shopify and Google Maps and others), adding 1.2 MB and 328 ms of main-thread time.

  • Improve image delivery

    263 KiB

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

  • Google CDN adds 109 ms

    109 ms

    Google CDN costs a phone 109 ms of main-thread work and 429 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 103 ms

    103 ms

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

  • Font display

    200 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

  • Render-blocking requests

    150 ms

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

  • Use efficient cache lifetimes

    127 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    46 KiB

    About 46 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    24 KiB

    24 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    15 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix80
  • First Contentful Paint: 4.4 s

    4.4 s

    The first text or image appears after 4.4 s on a phone. Good is under 1.8 s.

  • Speed Index: 8.2 s

    8.2 s

    Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Each product is custom blended specifically for YOU! We tho…”. Most of its time is element render delay (2.6 s).

  • Time to Interactive: 7.3 s

    7.3 s

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

  • 11 images without width and height

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 25 ms

    25 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 162 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 162 requests on a phone: scripts 1.2 MB (57), other files 815 KiB (79) and images 321 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (91 KiB) 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.

  • 2 images below the first screen load straight away

    2 images further down the page (58 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.73 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8692
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

  • 13 form fields without a label

    13 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10081
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 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 long (165 characters)

    Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 97 internal links, 8 external

    The homepage links to 97 pages on mashlabs.shop and 8 external pages.

5 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “MASH Labs - Create Your Own Skin Care Products”.

  • Canonical URL set

    The canonical URL is https://mashlabs.shop/.

  • 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://mashlabs.shop/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.

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 (1,124 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://mashlabs.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://mashlabs.shop/collections/skin-care, https://mashlabs.shop/collections/body-care/body_care, https://mashlabs.shop/pages/how-it-works and https://mashlabs.shop/products/book-an-appointment have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://mashlabs.shop/collections/skin-care, https://mashlabs.shop/products/custom-bb-cream, https://mashlabs.shop/products/custom-toner, https://mashlabs.shop/products/custom-cleanser, https://mashlabs.shop/products/custom-serum and https://mashlabs.shop/collections/body-care/body_care 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 33 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 to fixGoogle 9687
  • 27 small tap targets

    27 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix90
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 424 words of copy

    The homepage carries about 424 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe us”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Book Online”, “Contact Us” and “Lab Book (Recipe Book)”.

  • 15 short forms

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

  • Social proof on the page

    Social proof on the homepage: 36 testimonial or review blocks and 4 customer or partner logos.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 3 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 mashlabs.shop, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

ds-cdn.com · bookthatapp.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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mashlabs.shop, including 11 speed issues, 3 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

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