Website review, no card needed

maykers.com logo

maykers.com website review

Visit site (opens in a new tab)Reviewed 25 October 202637 issues · 76 checks

This review found 37 issues worth fixing on maykers.com, 8 of them high impact, across 76 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

Real-visitor load time (LCP)75th percentile, phones
4.2 s2.8 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.1 s
May 9, 20264.0 s
May 16, 20263.8 s
May 23, 20263.7 s
May 30, 20263.7 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20264.0 s
Jun 27, 20264.1 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20263.7 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.5 s
Sep 12, 20263.4 s
Sep 19, 20263.2 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
337 ms207 msMay 2Oct 17277 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026222 ms
May 9, 2026222 ms
May 16, 2026225 ms
May 23, 2026228 ms
May 30, 2026233 ms
Jun 6, 2026238 ms
Jun 13, 2026241 ms
Jun 20, 2026248 ms
Jun 27, 2026260 ms
Jul 4, 2026275 ms
Jul 11, 2026295 ms
Jul 18, 2026311 ms
Jul 25, 2026322 ms
Aug 1, 2026320 ms
Aug 8, 2026313 ms
Aug 15, 2026308 ms
Aug 22, 2026302 ms
Aug 29, 2026302 ms
Sep 5, 2026305 ms
Sep 12, 2026308 ms
Sep 19, 2026309 ms
Sep 26, 2026304 ms
Oct 3, 2026294 ms
Oct 10, 2026281 ms
Oct 17, 2026277 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 maykers.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maykers.com at 0.4 s0.4 s
  2. maykers.com at 0.8 s0.8 s
  3. maykers.com at 1.1 s1.1 s
  4. maykers.com at 1.5 s1.5 s
  5. maykers.com at 1.9 s1.9 s
  6. maykers.com at 2.3 s2.3 s
  7. maykers.com at 2.6 s2.6 s
  8. maykers.com at 3.0 s3.0 s

Speed

6 to fix50
  • Reduce unused JavaScript

    2.8 s · 653 KiB

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

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    350 ms · 58 KiB

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

  • 14 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

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

  • Main-thread work: 2.4 s

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

  • Legacy JavaScript

    200 ms · 32 KiB

    Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Optanon, Google Tag Manager and Google/Doubleclick Ads), adding 188 KiB and 104 ms of main-thread time.

  • Reduce unused CSS

    37 KiB

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

  • 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: 9 ms

    9 ms

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

Core Web Vitals

11 to fix67
  • 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.

  • Largest Contentful Paint: 10.8 s

    10.8 s

    Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking “Accept All Cookies”, you agree to the storing …”.

  • Time to Interactive: 11.0 s

    11.0 s

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

  • Total Blocking Time: 998 ms

    998 ms

    Scripts block taps and scrolling for 998 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 2.8 s

    2.8 s

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

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

    +26%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 997 ms

    997 ms

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

  • Speed Index: 4.1 s

    4.1 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 1 image without width and height

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

4 checks passed
  • Real-user INP: 88 ms

    88 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 26% faster for real visitors

    -26%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.48 g

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

4 checks passed
  • Page weight: 1.7 MB in 70 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 70 requests on a phone: scripts 1.3 MB (26), other files 150 KiB (28) and fonts 108 KiB (7). That is a lean page.

  • 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

5 to fixGoogle 8792
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

5 to fixGoogle 9283
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.kramp.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 29 internal links, 0 external

    The homepage links to 29 pages on maykers.com and 0 external pages.

4 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Europe's largest specialist of spare parts and accessories in Agriculture and Forest & Grasscare industries. Wide assor…”.

  • One H1 headline

    Your main headline reads: “Choose your language”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Kramp - Empowering you to move forward - Kramp”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, 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.kramp.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.

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

Other pages

4 to fix75
  • 1 linked page hidden from search

    https://www.kramp.com/shop-pl/en is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages share a title

    https://www.kramp.com/shop-hr/hr, https://www.kramp.com/shop-ie/en, https://www.kramp.com/shop-pl/en, https://www.kramp.com/shop-hu/hu and https://www.kramp.com/shop-at/de all use the title “KRAMP - It's that easy”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.kramp.com/shop-hr/hr, https://www.kramp.com/shop-ie/en, https://www.kramp.com/shop-pl/en, https://www.kramp.com/shop-hu/hu and https://www.kramp.com/shop-at/de have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.kramp.com/shop-hu/hu has 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 28 found) and read each the way a search engine does.

3 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 title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 26 small tap targets

    26 of 31 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 “Uncaught TypeError: Cannot read properties of undefined (reading 'controller')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Only about 71 words

    The homepage has only about 71 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “/shop-es/es” and “/shop-be/nl”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “/shop-es/es”, “/shop-be/nl” and “/shop-be/fr”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 maykers.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
Next.js
Analytics
Google Tag Manager
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on maykers.com, including 17 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

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