Cached Analysis
This analysis was performed 4 months ago (12.05.2026 10:22). The website may have changed since then.
Average
Site needs optimization in many areas
Bridge the gap. Get a free action plan to reach score 80+ within 24h.
Get a free improvement plan
Your site scored 56/100. We will analyze your results and send you a detailed plan to improve your SEO.
Thank you!
We will send you the improvement plan within 24 hours.
⚠️ Critical Issues (4)
-
24/100
Core Web Vitals
Too many render-blocking scripts (7) - significantly impacts LCP, 49 of 57 images lack width/height - major CLS risk, 7 synchronous scripts in head may cause long tasks
Recommendation: Move scripts to end of body or add async/defer - 7 blocking scripts detected -
50/100
Robots & Sitemap
Missing Sitemap declaration in robots.txt, Sitemap.xml file not found
Recommendation: Add "Sitemap: https://yourdomain.com/sitemap.xml" line to robots.txt -
55/100
Mobile Friendliness
No media queries detected - page may not be responsive
Recommendation: Add CSS media queries for responsive design (@media (max-width: 768px)) -
65/100
Meta Tags
Title too short (24 characters), Description too long (286 characters, may be truncated), Missing charset declaration
Recommendation: Extend title to 30-60 characters for better search visibility
Your site loads slowly. Our hosting runs on fast NVMe drives with built-in CDN, HTTP/2, and Brotli compression — measurably faster.
Category Scores
Meta Information
29/100Content
92/100Resources
64/100Technical SEO
54/100Priority Recommendations
Top 15Add Article/BlogPosting structured data - crucial for AI content understanding
Missing structured data
The page has no Schema.org markup that tells Google exactly what the content is (article, product, company, etc.).
You're not taking advantage of "rich snippets" - enhanced results with stars, prices, images.
Add appropriate Schema.org type (e.g., Article, Product, Organization) in JSON-LD format.
Page needs significant changes to be well-cited by AI systems - start with adding Schema.org and clear content structure
Missing structured data
The page has no Schema.org markup that tells Google exactly what the content is (article, product, company, etc.).
You're not taking advantage of "rich snippets" - enhanced results with stars, prices, images.
Add appropriate Schema.org type (e.g., Article, Product, Organization) in JSON-LD format.
Move scripts to end of body or add async/defer - 7 blocking scripts detected
Add explicit width and height to all images to prevent Cumulative Layout Shift
Use defer or async for all scripts - 7 sync scripts block interactivity
Add alt text to all images for better SEO and accessibility
Create and publish a sitemap.xml file containing all important pages
Add CSS media queries for responsive design (@media (max-width: 768px))
Add <meta charset="UTF-8"> in the <head> section
Enable gzip or brotli compression for HTML, CSS, JS - reduces size by up to 70%
No resource compression
Server does not compress text files (HTML, CSS, JS) before sending.
Data transfer is 60-80% larger than it could be. Page loads much slower.
Enable gzip or brotli compression in server configuration.
Add <meta property="og:image"> tag with an image at least 1200x630 pixels. Without it, Facebook shows a random or empty preview
Missing og:image
No image for social media. Shared links will be without graphics.
Posts without images get significantly fewer clicks and shares.
Add og:image with an image address minimum 1200x630 pixels.
Add Strict-Transport-Security header with max-age of at least 31536000 (1 year). This protects users against HTTPS downgrade attacks
Page is not secure (no HTTPS)
Your page doesn't use encrypted HTTPS connection. Browsers show "Not Secure" warning next to the address.
Google lowers rankings for pages without HTTPS. Users don't trust pages without the "padlock" in the address bar.
Install an SSL certificate (many hosts offer free Let's Encrypt) and redirect traffic to https://.
Add Content-Security-Policy header - the most effective protection against XSS attacks. Start with report-only mode: Content-Security-Policy-Report-Only
Missing security headers
The page doesn't send basic security headers that protect against attacks.
The page is more vulnerable to XSS, clickjacking, and other attacks.
Add headers: X-Content-Type-Options, X-Frame-Options, Content-Security-Policy.
Add X-Frame-Options: SAMEORIGIN header. This protects against clickjacking attacks where an attacker embeds your page in a hidden iframe
Missing security headers
The page doesn't send basic security headers that protect against attacks.
The page is more vulnerable to XSS, clickjacking, and other attacks.
Add headers: X-Content-Type-Options, X-Frame-Options, Content-Security-Policy.
🎯 Quick Wins
Best ROISchema.org Markup
ROI: 16-
Consider migrating microdata to JSON-LD - it is easier to maintain and preferred by Google
Missing structured data
The page has no Schema.org markup that tells Google exactly what the content is (article, product, company, etc.).
ImpactYou're not taking advantage of "rich snippets" - enhanced results with stars, prices, images.
How to fixAdd appropriate Schema.org type (e.g., Article, Product, Organization) in JSON-LD format.
Open Graph Protocol
ROI: 16- Add Open Graph tags (og:title, og:description, og:image, og:url) for better sharing on Facebook
Header Structure
ROI: 15- Keep only one H1 heading per page
-
Maintain logical heading hierarchy without skipping levels (H1 → H2 → H3)
Broken heading hierarchy
Headings should follow order: H1 → H2 → H3. Skips (e.g., H1 to H4) confuse screen readers and Google.
ImpactBlind users using screen readers may have navigation problems. Google understands structure worse.
How to fixMaintain logical hierarchy: H1 → H2 → H3 → H4 without skipping levels.
HTTP Headers Security
ROI: 15-
Add Strict-Transport-Security header with max-age of at least 31536000 (1 year). This protects users against HTTPS downgrade attacks
Page is not secure (no HTTPS)
Your page doesn't use encrypted HTTPS connection. Browsers show "Not Secure" warning next to the address.
ImpactGoogle lowers rankings for pages without HTTPS. Users don't trust pages without the "padlock" in the address bar.
How to fixInstall an SSL certificate (many hosts offer free Let's Encrypt) and redirect traffic to https://.
-
Add Content-Security-Policy header - the most effective protection against XSS attacks. Start with report-only mode: Content-Security-Policy-Report-Only
Missing security headers
The page doesn't send basic security headers that protect against attacks.
ImpactThe page is more vulnerable to XSS, clickjacking, and other attacks.
How to fixAdd headers: X-Content-Type-Options, X-Frame-Options, Content-Security-Policy.
Social Preview
ROI: 13.33-
Add <meta property="og:image"> tag with an image at least 1200x630 pixels. Without it, Facebook shows a random or empty preview
Missing og:image
No image for social media. Shared links will be without graphics.
ImpactPosts without images get significantly fewer clicks and shares.
How to fixAdd og:image with an image address minimum 1200x630 pixels.
- Add og:title tag - Facebook will use a dedicated title instead of the HTML title tag
Core Web Vitals
ROI: 12.2- Move scripts to end of body or add async/defer - 7 blocking scripts detected
- Add preload hints for critical resources (fonts, hero image, main CSS)
Detailed Results
26 analyzersStrona główna - CPU ZETO
Length: 24 charactersSpecjalizujemy się we wdrażaniu specjalistycznych systemów informatycznych. Tworzymy strony i portale WWW oraz projektujemy i uruchamiamy sieci komputerowe i instalacje teletechniczne. Nasza oferta obejmuje również sprzedaż i serwis sprzętu komputerowego, biurowego oraz kas fiskalnych.
Length: 286 characterswidth=device-width, initial-scale=1.0
pl-pl
HTML structure
Resources
Cache
Render-blocking resources: 6
Content structure
Answer format
Structured data
Authority signals
Weight breakdown by category
Compression
Minification
Internal links - redirected (1)
| URL | Code | Redirects to |
|---|---|---|
| http://www.cpu-zeto.pl/ | 302 | https://cpu-zeto.pl/ |
External links - broken (3)
| URL | Status | Suggestion |
|---|---|---|
| http://www.dell.com/pl | 403 | Remove or update |
| http://zeto.lublin.pl/ | 403 | Remove or update |
| http://www.zeto-kielce.com.pl/ | timeout | Remove or update |
External links - redirected (5)
| URL | Code | Redirects to |
|---|---|---|
| http://gov.pl/laptop-dla-nauczyciela | 301 | https://www.gov.pl/laptop-dla-nauczyciela |
| http://getagility.pl | 302 | https://e-mleczarnia.pl/ |
| http://www.kwbturow.pgegiek.pl/ | 301 | https://www.kwbturow.pgegiek.pl/ |
| http://www.rb.com/pl | 301 | https://www.rb.com/pl |
| http://www.elzab.com.pl/ | 301 | http://www.elzab.com.pl/pl/ |
pl-pl
Scalable
Character analysis
Additional features
Dofollow / Nofollow
Anchor text
Redirect chain (1 step)
www redirect
HTTPS redirect
Meta Refresh
JS redirect
Twitter/X
IncompleteSocial media image analysis
No available image or it could not be analyzed
Text readability
| Metric | Result |
|---|---|
| Flesch Reading Ease | 40.7 |
| Flesch-Kincaid Grade | 8.4 |
| Gunning Fog Index | 10.8 |
| Coleman-Liau Index | 12.0 |
| SMOG Index | 8.7 |
| Difficulty level | Difficult |
| Words per sentence (average) | 3.2 |
Structure
Content to HTML ratio
LCP - Details
INP - Details
CLS - Details
TTFB - Details
Resource Hints
Most frequent words (779 unique)
| # | Word | How many times | Density | |
|---|---|---|---|---|
| 1 | 75 | 23 | 1.80% |
|
| 2 | 64 | 21 | 1.64% |
|
| 3 | 25 | 21 | 1.64% |
|
| 4 | zeto | 19 | 1.49% |
|
| 5 | tel | 18 | 1.41% |
|
| 6 | cpu | 17 | 1.33% |
|
| 7 | więcej | 10 | 0.78% |
|
| 8 | systemu | 9 | 0.70% |
|
| 9 | sp | 8 | 0.63% |
|
| 10 | system | 8 | 0.63% |
|
Two-word phrases (68 unique)
| # | Phrase | How many times | Density | |
|---|---|---|---|---|
| 1 | 75 64 | 21 | 1.66% |
|
| 2 | 64 25 | 21 | 1.66% |
|
| 3 | cpu zeto | 17 | 1.34% |
|
| 4 | tel 75 | 9 | 0.71% |
|
| 5 | tel kom | 8 | 0.63% |
|
| 6 | zeto sp | 7 | 0.55% |
|
| 7 | jeleniej górze | 6 | 0.47% |
|
| 8 | na rynku | 6 | 0.47% |
|
| 9 | sp jeleniej | 4 | 0.32% |
|
| 10 | cdn xl | 4 | 0.32% |
|
Three-word phrases (46 unique)
| # | Phrase | How many times | Density | |
|---|---|---|---|---|
| 1 | 75 64 25 | 21 | 1.65% |
|
| 2 | tel 75 64 | 9 | 0.71% |
|
| 3 | cpu zeto sp | 6 | 0.47% |
|
| 4 | zeto sp jeleniej | 4 | 0.31% |
|
| 5 | sp jeleniej górze | 4 | 0.31% |
|
| 6 | cpu zeto pl | 4 | 0.31% |
|
| 7 | jeleniej górze jest | 3 | 0.24% |
|
| 8 | 64 25 173 | 3 | 0.24% |
|
| 9 | 25 173 75 | 3 | 0.24% |
|
| 10 | 173 75 64 | 3 | 0.24% |
|
Heading distribution
- Skok z H1 do H3 (pominięto H2)
Anchor text quality
Depth of linked URLs
Link location on the page
No images on the page
HTTP → HTTPS redirect
Security headers
| Keyword | Title | Description | H1 | Consistency |
|---|---|---|---|---|
| zeto | ✓ | ✗ | ✗ | 1/3 |
| rynku | ✗ | ✗ | ✗ | 0/3 |
| system | ✗ | ✓ | ✗ | 1/3 |
| systemu | ✗ | ✗ | ✗ | 0/3 |
| więcej | ✗ | ✗ | ✗ | 0/3 |
width=device-width, initial-scale=1.0
Font size
Tap targets
Media Queries
Responsive images
| Header | Status | Details |
|---|---|---|
| HSTS | No | none |
| Content-Security-Policy | No | none |
| X-Frame-Options | No | none |
| X-Content-Type-Options | No | none |
| Referrer-Policy | No | none |
| Permissions-Policy | No | none |
| X-XSS-Protection | No | none |
Add this badge to your website
Your website scored 56/100 in the full SEO analysis. Copy the HTML code and paste it into your footer or sidebar.
<a href="https://seometryka.pl" title="SEO Score 56/100 - tested with Seometryka.pl"><img src="https://seometryka.pl/badge/wynik/14725.svg?lang=en" alt="SEO Score 56/100 - tested with Seometryka.pl" height="28" loading="lazy"></a>
Your site needs professional help
With a score of 56/100, your site is losing customers and ranking. We can help — get a free improvement estimate within 24 hours.
Thank you!
We will contact you within 24 hours with a free improvement estimate for your site.