Your Website Score is

Similar Ranking

19
SEO STATS, ANALYSIS - WEBSITE REVIEW | RTSTORM TRACKER
rtstorm.it
19
SEO STATS, ANALYSIS - WEBSITE REVIEW | FSCLOUD TRACKER
fscloud.ovh
19
SIEBEL CRM LITTLE BLOG
siebel-crm.net
19
AUTOFIRENZE
autofirenze.biz
19
SALVIA-COMMUNITY.NET - WIR SIND DAS ORIGINAL!
salvia-community.net
19
HOME | ENGLISH COACHING AND MINDFULNESS PRACTICES SCHOOLOFESLYOGA
eslyoga.com
19
ADC | SPECIALIST RIG INSPECTION & AUDIT
adc-inspect.com

Latest Sites

19
SEO STATS, ANALYSIS - WEBSITE REVIEW | FSCLOUD TRACKER
fscloud.ovh
56
WEBSITE OPTIMIZATION AND DIGITAL AGENCY SALES TOOLS | WOORANK
woorank.com
20
YAHOO SÖK – WEBBSÖKNING
altavista.se
19
LIVE --- CAMS AND ADULT --- FOR---.
livewhoa.com

Top Technologies

Google Font API
Font Scripts
Apache
Web Servers
Nginx
Web Servers
WordPress
CMS
Font Awesome
Font Scripts
CloudFlare
CDN
Google Tag Manager
Tag Managers
Twitter Bootstrap
Web Frameworks

19 zusuh.cz Last Updated: 4 weeks

Success 62% of passed verification steps
Warning 15% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 89%
Best Practices Desktop Score 53%
SEO Desktop Score 73%
Progressive Web App Desktop Score 36%
Performance Mobile Score 58%
Best Practices Mobile Score 60%
SEO Mobile Score 75%
Progressive Web App Mobile Score 33%
Page Authority Authority 23%
Domain Authority Domain Authority 30%
Moz Rank 2.3/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 3 Characters
ZUŠ
Meta Description 0 Characters
NO DATA
Effective URL 20 Characters
https://www.zusuh.cz
Excerpt Page content
ZUŠ ...
Keywords Cloud Density
publikováno23 hradiště12 před11 základní11 měsíci9 uherské9 děti8 fotogalerie7 hudební7 školy7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
publikováno 23
hradiště 12
před 11
základní 11
měsíci 9
uherské 9
děti 8
fotogalerie 7
hudební 7
školy 7
Google Preview Your look like this in google search result
ZUŠ
https://www.zusuh.cz
ZUŠ ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~70.4 KB
Code Size: ~38.16 KB
Text Size: ~32.24 KB Ratio: 45.79%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Keep request counts low and transfer sizes small 89 requests • 2,322 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 726 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Reduce initial server response time Root document took 1,080 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 67 resources found
A long cache lifetime can speed up repeat visits to your page
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS Potential savings of 29 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Reduce unused JavaScript Potential savings of 218 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 24 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Serve images in next-gen formats Potential savings of 403 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 9 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Defer offscreen images Potential savings of 6 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Properly size images Potential savings of 276 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids enormous network payloads Total size was 2,322 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities 10 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Eliminate render-blocking resources Potential savings of 930 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 5 KiB
Optimized images load faster and consume less cellular data

Mobile

Mobile Screenshot
Serve images in next-gen formats Potential savings of 388 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Tap targets are not sized appropriately 82% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Serve static assets with an efficient cache policy 66 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 5.2 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint (3G) 11040 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Speed Index 7.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 6.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 5.2 s
First Meaningful Paint measures when the primary content of a page is visible
Document uses legible font sizes 99.94% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Avoids an excessive DOM size 726 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minimize third-party usage Third-party code blocked the main thread for 50 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize main-thread work 3.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 4,160 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Includes front-end JavaScript libraries with known security vulnerabilities 10 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Reduce unused CSS Potential savings of 29 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid long main-thread tasks 14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Does not use HTTPS 9 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoid chaining critical requests 23 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Properly size images Potential savings of 43 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Keep request counts low and transfer sizes small 88 requests • 2,347 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Reduce unused JavaScript Potential savings of 217 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Efficiently encode images Potential savings of 5 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint 6.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids enormous network payloads Total size was 2,347 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce initial server response time Root document took 1,210 ms
Keep the server response time for the main document short because all other requests depend on it
Defer offscreen images Potential savings of 6 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Domain Available

Domain (TDL) and Typo Status
zusuh.co Available
zusuh.us Available
zusuh.com Available
zusuh.org Available
zusuh.net Available
zsuh.cz Available
ausuh.cz Available
wusuh.cz Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Tue, 24 Aug 2021 21:44:04 GMT
server: Apache
x-powered-by: Nette Framework
x-frame-options: SAMEORIGIN
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
vary: X-Requested-With
set-cookie: nette-browser=jdurj1n9pv; path=/; httponly
set-cookie: PHPSESSID=e04c659c61a4e9e6b0b20bc76f08352f; path=/; HttpOnly
content-type: text/html; charset=utf-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments