Website review, no card needed
planetcare.gr website review
Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 80 checks
This review found 28 issues worth fixing on planetcare.gr, 8 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 821 ms |
| May 30, 2026 | 836 ms |
| Jun 6, 2026 | 804 ms |
| Jun 13, 2026 | 849 ms |
| Jun 20, 2026 | 847 ms |
| Jun 27, 2026 | 845 ms |
| Jul 4, 2026 | 906 ms |
| Jul 11, 2026 | 867 ms |
| Jul 18, 2026 | 898 ms |
| Jul 25, 2026 | 894 ms |
| Aug 1, 2026 | 840 ms |
| Aug 8, 2026 | 875 ms |
| Aug 15, 2026 | 882 ms |
| Aug 22, 2026 | 880 ms |
| Aug 29, 2026 | 920 ms |
| Sep 5, 2026 | 946 ms |
| Sep 12, 2026 | 899 ms |
| Sep 19, 2026 | 900 ms |
| Sep 26, 2026 | 894 ms |
| Oct 3, 2026 | 850 ms |
| Oct 10, 2026 | 900 ms |
| Oct 17, 2026 | 899 ms |
| Oct 24, 2026 | 892 ms |
| Oct 31, 2026 | 872 ms |
| Nov 7, 2026 | 837 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 215 ms |
| May 30, 2026 | 208 ms |
| Jun 6, 2026 | 218 ms |
| Jun 13, 2026 | 235 ms |
| Jun 20, 2026 | 242 ms |
| Jun 27, 2026 | 240 ms |
| Jul 4, 2026 | 261 ms |
| Jul 11, 2026 | 253 ms |
| Jul 18, 2026 | 252 ms |
| Jul 25, 2026 | 242 ms |
| Aug 1, 2026 | 222 ms |
| Aug 8, 2026 | 215 ms |
| Oct 17, 2026 | 204 ms |
| Oct 24, 2026 | 206 ms |
| Oct 31, 2026 | 218 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Use efficient cache lifetimes
350 ms · 229 KiB75 files are served with short cache lifetimes, so returning visitors download them again (229 KiB).
Improve image delivery
350 ms · 165 KiB8 images could be 165 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
2,772 HTML elements
The page has 2,772 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 43 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 11 ms of it running JavaScript. That is comfortably low.
Server response: 119 ms
119 msYour server sent the HTML in 119 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Time to Interactive: 5.7 s
5.7 sThe page becomes fully interactive after 5.7 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 215 ms to 218 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 411 ms
411 msReal visitors wait 411 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
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.019
0.019The layout barely moves while loading (CLS 0.019, 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
Page weight: 2.5 MB in 81 requests
2.5 MBYour homepage downloads 2.5 MB in 81 requests on a phone: images 2.2 MB (74), fonts 269 KiB (6) and HTML 91 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (45 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA commands must have an accessible name (36 elements)
ARIA commands must have an accessible name: 36 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
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 (112 elements)
All page content should be contained by landmarks: 112 elements on the page fail this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
111 links crawlers can't follow
111 links have no real href, so search engines can't follow them.
Title is short (13 characters)
Your title is only 13 characters: “planetcare.gr”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 3 problems
Structured data found (Organization, Place, Store and WebSite) but with 3 problems, for example “Organization: missing name”.
290 internal links, 6 external
The homepage links to 290 pages on planetcare.gr and 6 external pages.
5 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Στο PlanetCare, η ομορφιά & η υγεία λάμπουν δίχως όρια! Ένας ολόκληρος πλανήτης ομορφιάς & ευεξίας σας περιμένει για να…”.
Canonical URL set
The canonical URL is https://www.planetcare.gr/.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.planetcare.gr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.planetcare.gr/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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (528 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://www.planetcare.gr/antiliaki-prostasia and https://www.planetcare.gr/antiliaki-prostasia-1 all use the title “Αντηλιακή Προστασία”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.planetcare.gr/prosopo, https://www.planetcare.gr/antiliaki-prostasia, https://www.planetcare.gr/antigiransi, https://www.planetcare.gr/enudatosi, https://www.planetcare.gr/katharismos and https://www.planetcare.gr/makigiaz and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 118 found) and read each the way a search engine does.
5 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 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “fbq is not defined”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
74 of 85 tappable elements near the top are at least 24 px.
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.
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 158 words
The homepage has only about 158 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
18 calls to action
The homepage has 18 calls to action, for example “Buy Now”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 2 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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 planetcare.gr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on planetcare.gr, including 9 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.