Website review, no card needed
matrova.com website review
Visit site (opens in a new tab)Reviewed 10 November 202636 issues · 82 checks
This review found 36 issues worth fixing on matrova.com, 13 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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
85B- #14,086 of 102,641 reviewed websitesbeats 82%
- #8,815 of 57,056 online storesbeats 79%
- #8,566 of 51,912 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 148 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 150 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 133 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 124 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 137 ms |
| Nov 7, 2026 | 153 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
Render-blocking requests
1.1 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 130 KiBAbout 130 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.
2,966 HTML elements
The page has 2,966 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 194 ms
194 msShopify costs a phone 194 ms of main-thread work and 447 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.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 484 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 492 KiB and 198 ms of main-thread time.
Reduce unused CSS
150 ms · 24 KiBAbout 24 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
16 KiB5 files are served with short cache lifetimes, so returning visitors download them again (16 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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (4.9 s).
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.109
0.109The layout shifts by 0.109 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 4.1 s
4.1 sThe page becomes fully interactive after 4.1 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 148 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 192 ms
192 msReal visitors wait 192 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 656 ms
656 msReal visitors wait 656 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.5 MB in 242 requests
6.5 MBYour homepage downloads 6.5 MB in 242 requests on a phone: media 4.5 MB (1), scripts 615 KiB (111) and other files 579 KiB (58). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
matrovaclear.png 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.8 g of CO₂ per visit
1.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.83 g of CO₂e: 219.5 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
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
81 internal links, 9 external
The homepage links to 81 pages on matrova.com and 9 external pages.
5 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “Matrova | Premium Gaming Mouse Pads for Professional Gamers”.
Canonical URL set
The canonical URL is https://matrova.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://matrova.com/sitemap.xml.
AI search readiness
4 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,330 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://matrova.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://matrova.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 page points its canonical at the homepage
https://matrova.com/products/custom-mousepad declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 linked page hidden from search
https://matrova.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://matrova.com/products/custom-mousepad all use the title “Matrova | Premium Gaming Mouse Pads for Professional Gamers”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://matrova.com/collections/all, https://matrova.com/customer_authentication/redirect and https://matrova.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://matrova.com/customer_authentication/redirect, https://matrova.com/products/yang-speed-glass-pad, https://matrova.com/products/yin-balance-glass-pad, https://matrova.com/products/pink-storm, https://matrova.com/products/violet-mist and https://matrova.com/products/vein and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://matrova.com/customer_authentication/redirect, https://matrova.com/collections/mouse-pad, https://matrova.com/pages/imagine-for-custom, https://matrova.com/products/custom-mousepad, https://matrova.com/products/ozi and https://matrova.com/products/shadow-hunt took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
2 broken images
2 images failed to load on a phone, for example https://matrova.com/.
6 small tap targets
6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 393 words of copy
The homepage carries about 393 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe”.
3 calls to action
The homepage has 3 calls to action, for example “CONTACT INFORMATION” and “Contact information”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
11 other companies contacted
Loading the homepage contacts 11 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 matrova.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ymq Product Options · Inbox · Judge Me Reviews
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
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on matrova.com, including 11 speed issues, 3 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.