Your Website Score is

Similar Ranking

54
LEEDS BECKETT UNIVERSITY
leedsbeckett.ac.uk
54
JIHOČESKÁ UNIVERZITA V ČESKÝCH BUDĚJOVICÍCH
jcu.cz
54
UNIR - LA UNIVERSIDAD A DISTANCIA 100% ONLINE
unir.net
54
UNIVERSIDAD DE CÓRDOBA
uco.es
53
UNIVERSIDAD EUROPEA: EDUCACIÓN Y FORMACIÓN EN ESPAÑA | UE
universidadeuropea.es
53
DIAS – DUBLIN INSTITUTE FOR ADVANCED STUDIES
dias.ie
53
UNIVERSITAT AUTÒNOMA DE BARCELONA - UAB BARCELONA
uab.cat

54 jcu.cz Last Updated: 4 months

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

Desktop

Mobile

Performance Desktop Score 67%
Best Practices Desktop Score 85%
SEO Desktop Score 73%
Progressive Web App Desktop Score 38%
Performance Mobile Score 36%
Best Practices Mobile Score 77%
SEO Mobile Score 76%
Progressive Web App Mobile Score 41%
Page Authority Authority 45%
Domain Authority Domain Authority 55%
Moz Rank 4.5/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 43 Characters
JIHOČESKÁ UNIVERZITA V ČESKÝCH BUDĚJOVICÍCH
Meta Description 0 Characters
NO DATA
Effective URL 17 Characters
http://www.jcu.cz
Excerpt Page content
Jihočeská univerzita v Českých Budějovicích Login search using Google...
Keywords Cloud Density
data15 cycle14 faculty11 university10 bohemia6 south6 slider5 international4 search4 news4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
data 15
cycle 14
faculty 11
university 10
bohemia 6
south 6
slider 5
international 4
search 4
news 4
Google Preview Your look like this in google search result
JIHOČESKÁ UNIVERZITA V ČESKÝCH BUDĚJOVICÍCH
http://www.jcu.cz
Jihočeská univerzita v Českých Budějovicích Login search using Google...
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~32.41 KB
Code Size: ~23.77 KB
Text Size: ~8.64 KB Ratio: 26.65%

Estimation Traffic and Earnings

1,145
Unique Visits
Daily
2,118
Pages Views
Daily
$4
Income
Daily
32,060
Unique Visits
Monthly
60,363
Pages Views
Monthly
$100
Income
Monthly
370,980
Unique Visits
Yearly
711,648
Pages Views
Yearly
$1,056
Income
Yearly

Desktop

Desktop Screenshot
Minify JavaScript Potential savings of 15 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 80 requests • 1,466 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 31 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.3 s
Time to interactive is the amount of time it takes for the page to become fully 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
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 4 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 29 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 182 KB
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 73 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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
Reduce server response times (TTFB) Root document took 1,000 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,040 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Defer offscreen images Potential savings of 16 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,466 KB
Large network payloads cost users real money and are highly correlated with long load times
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 33 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
Avoids an excessive DOM size 358 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)

Mobile

Mobile Screenshot
Server response times are low (TTFB) Root document took 200 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 6,110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 110 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 320 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 16 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Speed Index 6.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 962 KB
Large network payloads cost users real money and are highly correlated with long load times
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Minimize main-thread work 2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 6.2 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 33 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
Avoids an excessive DOM size 341 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)
Minify JavaScript Potential savings of 15 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 6.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 75 requests • 962 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 29 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 390 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 8.2 s
Time to interactive is the amount of time it takes for the page to become fully 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
First Contentful Paint (3G) 12096 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 50 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 4 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 97% 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
Document uses legible font sizes 100% 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
Remove unused CSS Potential savings of 28 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 47 KB
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 69 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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

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
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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

347

Local Rank: CZ / Users: 92.7% / PageViews: 98.3%

120,396

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Tue, 03 Mar 2020 19:14:22 GMT
Server: Zope/(2.13.22, python 2.7.6, linux2) ZServer/1.1
Content-Language: cs
Expires: Sat, 01 Jan 2000 00:00:00 GMT
X-Ua-Compatible: IE=edge,chrome=1
X-Frame-Options: SAMEORIGIN
Content-Type: text/html;charset=utf-8
X-Varnish-TTL: -1.000
X-Varnish-Action: FETCH (deliver - not cacheable)
Content-Length: 39396
Accept-Ranges: bytes
X-Varnish: 93851174
Via: 1.1 varnish
X-Varnish-Age: 0
Age: 0
X-Cache: MISS
DNS Records DNS Resource Records associated with a hostname
View DNS Records