Website review, no card needed

qmsmedicosmetics.com logo

qmsmedicosmetics.com website review

Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 86 checks

This review found 34 issues worth fixing on qmsmedicosmetics.com, 8 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.5 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
143 ms99 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026110 ms
May 30, 2026106 ms
Jun 6, 2026112 ms
Jun 13, 2026110 ms
Jun 20, 2026120 ms
Jun 27, 2026122 ms
Jul 4, 2026118 ms
Jul 11, 2026111 ms
Jul 18, 2026104 ms
Jul 25, 2026114 ms
Aug 1, 2026122 ms
Aug 8, 2026128 ms
Aug 15, 2026136 ms
Aug 22, 2026121 ms
Aug 29, 2026121 ms
Sep 5, 2026120 ms
Sep 12, 2026121 ms
Sep 19, 2026129 ms
Sep 26, 2026108 ms
Oct 3, 2026115 ms
Oct 10, 2026114 ms
Oct 17, 2026111 ms
Oct 24, 2026138 ms
Oct 31, 2026129 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

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

How it loaded on a phone

  1. qmsmedicosmetics.com at 0.7 s0.7 s
  2. qmsmedicosmetics.com at 1.4 s1.4 s
  3. qmsmedicosmetics.com at 2.2 s2.2 s
  4. qmsmedicosmetics.com at 2.9 s2.9 s
  5. qmsmedicosmetics.com at 3.6 s3.6 s
  6. qmsmedicosmetics.com at 4.3 s4.3 s
  7. qmsmedicosmetics.com at 5.1 s5.1 s
  8. qmsmedicosmetics.com at 5.8 s5.8 s

Speed

9 to fix65
  • Render-blocking requests

    1.5 s

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65. 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 (Klaviyo, Facebook and Google Tag Manager and others), adding 1.8 MB and 738 ms of main-thread time.

  • Reduce unused JavaScript

    310 ms · 603 KiB

    About 603 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • Improve image delivery

    500 ms · 320 KiB

    14 images could be 320 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 369 KiB

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

  • Main-thread work: 3.0 s

    A phone's processor spends 3.0 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Klaviyo adds 209 ms

    209 ms

    Klaviyo costs a phone 209 ms of main-thread work and 524 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 94 ms

    94 ms

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

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    49 KiB

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

  • Reduce unused CSS

    39 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 17.2 s

    17.2 s

    Your largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 20.9 s

    20.9 s

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

  • Tap response (INP) got 20% slower for real visitors

    +20%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • 6 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 129 ms

    129 ms

    Real visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 661 ms

    661 ms

    Real visitors wait 661 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 149 ms

    149 ms

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

  • Cumulative Layout Shift: 0.057

    0.057

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

Images and page weight

4 to fix36
  • Page weight: 7.2 MB in 391 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 391 requests on a phone: images 4.2 MB (56), scripts 1.9 MB (135) and other files 862 KiB (156). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    The_COLLAgen3D_Discovery_Set.svg weighs 2.8 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    840 KiB

    2 images are downloaded at several times the size a phone draws them, for example The_COLLAgen3D_Discovery_Set.svg at 1,000 px wide, shown at 280 px. Resized copies would save about 840 KiB.

  • An image on the first screen is lazy-loaded

    heatwave-essentialsqms-medicosmetics-usa-and-north-america-4 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).

  • 3 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.05 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 9593
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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 8586
  • Title is long (94 characters)

    Your title is 94 characters, so Google will cut it off around 60: “QMS Medicosmetics | Revolutionary Premium Skincare – QMS Medicosmetics - USA and North Am…”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “HYDRAFilling LIP BALM”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 156 internal links, 5 external

    The homepage links to 156 pages on qmsmedicosmetics.com and 5 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Satisfying your highest demands in skincare, QMS is an internationally renowned premium doctor brand offering science-l…”.

  • Canonical URL set

    The canonical URL is https://www.qmsmedicosmetics.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.qmsmedicosmetics.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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.qmsmedicosmetics.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.qmsmedicosmetics.com/collections/all and https://www.qmsmedicosmetics.com/collections/view-all 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 85 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    2 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 2 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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 739 words of copy

    The homepage carries about 739 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 NOW”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “SHOP”, “SHOP ALL” and “Bestsellers Shop Now”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 20 cookies set on arrival

    20

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

  • 42 other companies contacted

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

Apps your storefront loads

Cartbot · Klaviyo Email Marketing Sms · Seolab · Sitemap Noindex Pro Seo · Forms · Booster Kit By Qikify · Geolocation Markets Selector · Deco Labels Badges · rise-ai.com · adroll.com

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
SvelteKit
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Teningen

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on qmsmedicosmetics.com, including 15 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