Website review, no card needed
adtdental.com website review
Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 68 checks
This review found 39 issues worth fixing on adtdental.com, 16 of them high impact, across 68 checks. The most urgent: improve image delivery. 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
62DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
6.0 s
Speed
Improve image delivery
17.4 s · 3.6 MB9 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.4 s faster on a phone.
Render-blocking requests
1.2 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
150 ms · 334 KiB14 files are served with short cache lifetimes, so returning visitors download them again (334 KiB).
Reduce unused CSS
300 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
imgstore.io adds 0 ms
0 msimgstore.io costs a phone 0 ms of main-thread work and 388 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.
5 third-party services on the page
5 third-party services load with your homepage (envato-static.com, Cloudflare and Bing Ads and others), adding 695 KiB and 58 ms of main-thread time.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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, 98 ms of it running JavaScript. That is comfortably low.
Server response: 228 ms
228 msYour server sent the HTML in 228 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DEWI11 | Official Situs Game Online Terlengkap Dengan Fitur…”.
Time to Interactive: 22.1 s
22.1 sThe page becomes fully interactive after 22.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.509
0.509The layout shifts by 0.509 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 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.
1 checks passed
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
2 images over 500 KB
2 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.
Page weight: 4.2 MB in 32 requests
4.2 MBYour homepage downloads 4.2 MB in 32 requests on a phone: images 4.0 MB (18), stylesheets 77 KiB (3) and scripts 77 KiB (8). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
1.8 MB8 images are downloaded at several times the size a phone draws them, for example banner.png at 1,254 px wide, shown at 326 px. Resized copies would save about 1.8 MB.
9 images in older formats
9 images (3.9 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.
6 images below the first screen load straight away
6 images further down the page (439 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 142.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
<svg> elements with an img or image role must have alternative text (1 element)
<svg> elements with an img or image role must have alternative 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.
All page content should be contained by landmarks (41 elements)
All page content should be contained by landmarks: 41 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “DEWI11 | Official Situs Game Online Terlengkap Dengan Fitur Modern 2026”.
3 H1 headlines
There are 3 <h1> headlines (“DEWI11 | Official Situs Game Online Terlengkap De…”, “DEWI11 | Official Situs Game Online Terlengkap De…” and “DEWI11 | Official Situs Game Online Terlengkap De…”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (BreadcrumbList, FAQPage, Organization and Product) but with 2 problems, for example “Product: image is not an absolute URL ("img/dewi11-logo.gif")”.
No XML sitemap
No XML sitemap at https://occuperlesenfants.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.
151 internal links, 49 external
The homepage links to 151 pages on adtdental.com and 49 external pages.
4 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “DEWI11 menghadirkan platform game online dengan koleksi permainan beragam, akses praktis, fitur modern, serta layanan p…”.
Canonical URL set
The canonical URL is https://occuperlesenfants.com/comment-dessiner-des-animaux-doodles-tete-danimal-facile.
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://occuperlesenfants.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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (938 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://occuperlesenfants.com/item_support/what_is_item_support/8988002, which answers with an error. Visitors hit a dead end and search engines drop it.
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
Best practices
10 small tap targets
10 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute viewBox: Unexpected end of attribute. Expected number, "0 0 1414".”.
No character set
No character set is declared, so some characters can render as gibberish.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 683 words of copy
The homepage carries about 683 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Ads (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 1 of them by other companies (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.
5 other companies contacted
Loading the homepage contacts 5 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 adtdental.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Company
- Headquarters
- Minneapolis
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on adtdental.com, including 12 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.