Website review, no card needed

donit.eu logo

donit.eu website review

Visit site (opens in a new tab)Reviewed 2 November 202640 issues · 82 checks

This review found 40 issues worth fixing on donit.eu, 9 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.

  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
3.4 s2.6 sMay 16Oct 312.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Oct 24, 20262.8 s
Oct 31, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
117 ms67 msMay 16Oct 3177 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202677 ms
May 23, 202680 ms
May 30, 202693 ms
Jun 6, 2026104 ms
Jun 13, 2026111 ms
Jun 20, 2026101 ms
Jun 27, 202694 ms
Jul 4, 202688 ms
Jul 11, 202682 ms
Jul 18, 202676 ms
Jul 25, 202673 ms
Aug 1, 202677 ms
Aug 8, 202678 ms
Aug 15, 202681 ms
Aug 22, 202684 ms
Aug 29, 202678 ms
Sep 5, 202679 ms
Sep 12, 202678 ms
Sep 19, 202674 ms
Sep 26, 202680 ms
Oct 3, 202681 ms
Oct 10, 202679 ms
Oct 17, 202683 ms
Oct 24, 202677 ms
Oct 31, 202677 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 donit.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix66
  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    750 ms · 514 KiB

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

  • Improve image delivery

    1,021 KiB

    8 images could be 1,021 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 140 KiB

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

  • Font display

    450 ms

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

  • Reduce unused CSS

    150 ms · 93 KiB

    About 93 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (LinkedIn, Cookiebot and Google CDN and others), adding 377 KiB and 203 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 130 ms

    130 ms

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

Core Web Vitals

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1# Gasket Materials Production Research & Development Quali…”.

  • Time to Interactive: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). 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.

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

4 checks passed
  • Real-user INP: 74 ms

    74 ms

    Real visitors wait 74 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.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    ChatGPT-Image-22.-sep.-2026-08_58_37-700x467.png weighs 621 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.5 MB in 67 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 67 requests on a phone: images 1.7 MB (19), scripts 300 KiB (25) and media 211 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (995 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.

  • 3 images below the first screen load straight away

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

  • 1 image far larger than shown

    240 KiB

    1 image is downloaded at several times the size a phone draws it, for example eco-vadis-2026-donit.png at 1,667 px wide, shown at 130 px. Resized copies would save about 240 KiB.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

Accessibility

6 to fixGoogle 7490
  • 27 images without alt text

    27 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 6 links without text

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

  • 5 form fields without a label

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

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

5 to fixGoogle 8379
  • Title is short (20 characters)

    Your title is only 20 characters: “DONIT – Gasket Seals”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 9 H1 headlines

    There are 9 <h1> headlines (“DONIT��� Latest News & Events”, “Upcomming events / News” and “Slovenian hydrogen initiative SloH2U signed in Pl…”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • No X (Twitter) card tag

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

  • 130 internal links, 26 external

    The homepage links to 130 pages on donit.eu and 26 external pages.

4 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “DONIT is one of the leading companies in gasket materials and gasket sheets production.”.

  • Structured data in place

    Structured data found: BreadcrumbList and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://donit.eu/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.

  • No llms.txt

    There is no https://donit.eu/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 (570 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 15 pages share a meta description

    https://donit.eu/si, https://donit.eu/gaskets, https://donit.eu/gaskets/gaskets, https://donit.eu/application-engineering, https://donit.eu/certification-and-services and https://donit.eu/at-a-glance and 2 others use the same meta description. A description written for each page earns more clicks.

  • 5 pages slow to respond

    https://donit.eu/si, https://donit.eu/gasket-sheets, https://donit.eu/gasket-sheets/gasket-sheets/tesnit, https://donit.eu/gasket-sheets/gasket-sheets/doniflex and https://donit.eu/gaskets took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.

7 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 meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 6587
  • 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”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • Only about 174 words

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

  • 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
  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “General contact form” and “Enews sign up”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 13 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 donit.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Hosting
Optimus IT d.o.o.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on donit.eu, including 15 speed issues, 5 SEO issues and 4 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