Website review, no card needed
mirka.com website review
Visit site (opens in a new tab)Reviewed 19 November 202629 issues · 75 checks
This review found 29 issues worth fixing on mirka.com, 9 of them high impact, across 75 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 143 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 142 ms |
| Jul 25, 2026 | 141 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 147 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 146 ms |
| Nov 7, 2026 | 145 ms |
| Nov 14, 2026 | 147 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
Use efficient cache lifetimes
1.0 MB3 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 57
57/100Your mobile performance score is 57. 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 Tag Manager, TikTok and Cookiebot and others), adding 798 KiB and 748 ms of main-thread time.
Reduce unused JavaScript
300 ms · 349 KiBAbout 349 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.
Google Tag Manager adds 458 ms
458 msGoogle Tag Manager costs a phone 458 ms of main-thread work and 387 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 455 ms. During a long task the page ignores taps.
2,763 HTML elements
The page has 2,763 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Reduce unused CSS
68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
42 KiB2 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
1 checks passed
Server response: 229 ms
229 msYour server sent the HTML in 229 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.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.2 s
11.2 sThe page becomes fully interactive after 11.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”. Most of its time is element render delay (4.2 s).
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 447 ms
447 msScripts block taps and scrolling for 447 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 137 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 171 ms
171 msReal visitors wait 171 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.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 73 requests
5.7 MBYour homepage downloads 5.7 MB in 73 requests on a phone: other files 2.0 MB (17), media 1.9 MB (1) and scripts 1.0 MB (30). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
298 internal links, 9 external
The homepage links to 298 pages on mirka.com and 9 external pages.
8 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Abrasives, sanding tools and polishing compounds under the same roof. When it comes to an excellent finish, we have the…”.
One H1 headline
Your main headline reads: “Mirka Iridium™ – Now Improved”.
Title: 54 characters
Your title is a healthy 54 characters: “Abrasives, Sanding Tools & Polishing Compounds - Mirka”.
Canonical URL set
The canonical URL is https://www.mirka.com/en/.
Structured data in place
Structured data found: ItemList and Organization.
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.mirka.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.mirka.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,662 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.mirka.com/en/support/find-a-reseller-export has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.mirka.com/en/support/find-a-reseller-export and https://www.mirka.com/en/know-how/applications/belt-sanding/belt-range have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.mirka.com/en/know-how/applications/belt-sanding/belt-range took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 193 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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_FAILED”.
2 checks passed
Tap targets are thumb-sized
15 of 18 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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 682 words of copy
The homepage carries about 682 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Mirka Enables Body Shop Plastic Repairs” and “Join us at GrindingHub 2026”.
Analytics in place
Analytics detected: Google Tag Manager.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and TikTok Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 mirka.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Azure
Company
- Employees
- 1,800
- Founded
- 1943
- Headquarters
- Jeppo
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 mirka.com, including 17 speed 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.