Website review, no card needed
daycare.com.mk website review
Visit site (opens in a new tab)Reviewed 29 October 202630 issues · 54 checks
This review found 30 issues worth fixing on daycare.com.mk, 9 of them high impact, across 54 checks. The most urgent: render-blocking requests. 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
4.3 s53 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.3 s.
Improve image delivery
1.4 s · 326 KiB7 images could be 326 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
250 ms · 507 KiB107 files are served with short cache lifetimes, so returning visitors download them again (507 KiB).
3 third-party services on the page
3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 1,021 KiB and 621 ms of main-thread time.
Google CDN adds 568 ms
568 msGoogle CDN costs a phone 568 ms of main-thread work and 741 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.
Reduce unused CSS
450 ms · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
476 KiBAbout 476 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 107 ms
107 msYour server sent the HTML in 107 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “148.jpg”. Most of its time is resource load delay (3.9 s).
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 282 ms
282 msScripts block taps and scrolling for 282 ms in total while the page loads. Good is under 200 ms.
15 images without width and height
15 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
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 124 requests
3.7 MBYour homepage downloads 3.7 MB in 124 requests on a phone: images 1.2 MB (19), scripts 996 KiB (38) and fonts 949 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.4 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.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (3 elements).
1 link without text
1 link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
11 internal links, 3 external
The homepage links to 11 pages on daycare.com.mk and 3 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Кому да му ја доверите грижата”.
Title: 56 characters
Your title is a healthy 56 characters: “Day Care – Со Day Care решението е само на чекор од вас.”.
Canonical URL set
The canonical URL is https://daycare.com.mk/.
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://daycare.com.mk/wp-sitemap.xml.
AI search readiness
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://daycare.com.mk/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
5 linked pages are broken
Your homepage links to https://daycare.com.mk/griza-za-deca, https://daycare.com.mk/griza-za-vozrasni, https://daycare.com.mk/odrzuvanje-na-domot, https://daycare.com.mk/za-nas and https://daycare.com.mk/kontakt, which answer with an error. Visitors hit a dead end and search engines drop them.
Best practices
1 console error
1 error was logged to the browser console during Google's test (“requestStorageAccess: Permission denied.”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 4 testimonial or review blocks. 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 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 91 words
The homepage has only about 91 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.
1 checks passed
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
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 daycare.com.mk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on daycare.com.mk, including 15 speed issues, 3 SEO issues and 5 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.