Website review, no card needed
oodit.io website review
Visit site (opens in a new tab)Reviewed 9 November 202624 issues · 68 checks
This review found 24 issues worth fixing on oodit.io, 9 of them high impact, across 68 checks. The most urgent: use efficient cache lifetimes. 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
83BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
12.6 s · 2.9 MB28 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Improve image delivery
8.6 s · 1.7 MB6 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.6 s faster on a phone.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused CSS
340 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 340 ms faster on a phone.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
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.
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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 95 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DEMO AANVRAGEN MEER INFORMATIE ISO-GECERTIFICEERD”.
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
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
3 images over 500 KB
3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.5 MB3 images are downloaded at several times the size a phone draws them, for example troostwijk-by-accumin-vertical.jpg at 1,809 px wide, shown at 204 px. Resized copies would save about 1.5 MB.
Page weight: 2.9 MB in 29 requests
2.9 MBYour homepage downloads 2.9 MB in 29 requests on a phone: images 2.6 MB (16), fonts 203 KiB (5) and stylesheets 87 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (2.2 MB) 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.
1 image below the first screen load straight away
1 image further down the page (80 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No XML sitemap
No XML sitemap at https://oodit.nl/sitemap.xml, so Google discovers your pages only by following links.
41 internal links, 0 external
The homepage links to 41 pages on oodit.io and 0 external pages.
7 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Identificeer, monitor en beheers risico's in onze eenvoudig risico management software. Bekijk ook onze oplossing voor …”.
One H1 headline
Your main headline reads: “Manage al uw risico’s en preventie binnen uw bedrijf in één oplossing”.
Title: 33 characters
Your title is a healthy 33 characters: “Oodit - Risicomanagement Software”.
Canonical URL set
The canonical URL is http://oodit.nl/nl/.
Structured data in place
Structured data found: ImageObject, Organization, WebPage 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.
AI search readiness
No llms.txt
There is no https://oodit.nl/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 (424 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://oodit.nl/nl/iso-certification, whose canonical is https://oodit.nl/nl/solutions/maatwerk. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
4 small tap targets
4 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 391 words of copy
The homepage carries about 391 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “DEMO AANVRAGEN”.
5 calls to action
The homepage has 5 calls to action, for example “Contact met Oodit”, “Demo aanvragen” and “Contact”.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
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.
1 checks passed
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 oodit.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Signet B.V.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on oodit.io, including 10 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.