Your Website Score is

Similar Ranking

35
CREPS DES PAYS DE LA LOIRE
creps-pdl.sports.gouv.fr
35
ACCUEIL - UNIVERSITÉ DE MONS
web.umons.ac.be
35
FACULTY OF CONTEMPORARY ARTS
fsu.edu.rs
35
ESCOLA NAVAL
escolanaval.marinha.pt
35
OSTRAVSKÁ UNIVERZITA
osu.cz
35
POLITECHNIKA BIAŁOSTOCKA
pb.edu.pl
35
UNITBV - UNIVERSITATEA TRANSILVANIA DIN BRAȘOV
unitbv.ro

35 osu.cz Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 48%
Best Practices Desktop Score 62%
SEO Desktop Score 100%
Progressive Web App Desktop Score 27%
Performance Mobile Score 10%
Best Practices Mobile Score 62%
SEO Mobile Score 95%
Progressive Web App Mobile Score 26%
Page Authority Authority 45%
Domain Authority Domain Authority 49%
Moz Rank 4.5/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 20 Characters
OSTRAVSKÁ UNIVERZITA
Meta Description 74 Characters
Ostravská univerzita / Oficiální internetové stránky Ostravské univerzity.
Effective URL 18 Characters
https://www.osu.cz
Excerpt Page content
Ostravská univerzita Ostravská univerzita používá na svých webových stránkách soubory cookies i další ---ytické nástroje. Rozumím ...
Meta Keywords 1 Detected
Keywords Cloud Density
univerzita15 univerzity11 kontakty11 centrum10 ostravská7 fakulta7 poradenské7 studium7 činnost6 příspěvek6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
univerzita 15
univerzity 11
kontakty 11
centrum 10
ostravská 7
fakulta 7
poradenské 7
studium 7
činnost 6
příspěvek 6
Google Preview Your look like this in google search result
OSTRAVSKÁ UNIVERZITA
https://www.osu.cz
Ostravská univerzita / Oficiální internetové stránky Ostravské univerzity.
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~118.82 KB
Code Size: ~82 KB
Text Size: ~36.82 KB Ratio: 30.99%

Estimation Traffic and Earnings

1,777
Unique Visits
Daily
3,287
Pages Views
Daily
$6
Income
Daily
49,756
Unique Visits
Monthly
93,680
Pages Views
Monthly
$150
Income
Monthly
575,748
Unique Visits
Yearly
1,104,432
Pages Views
Yearly
$1,584
Income
Yearly

Desktop

Desktop Screenshot
Server response times are low (TTFB) Root document took 290 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 910 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 337 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 207 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 370 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 160 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.6 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 238 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.5 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).
Avoid enormous network payloads Total size was 8,531 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.2 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.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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 20 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
Avoid an excessive DOM size 1,264 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 18 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 337 requests • 8,531 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 113 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 5.5 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 27.5 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 30 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 2 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 150 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 1,568 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
User Timing marks and measures 15 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Mobile

Mobile Screenshot
Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 20 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
Avoid an excessive DOM size 1,264 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 18 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 5.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 338 requests • 15,720 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 115 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 900 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 29.1 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
Page load is not fast enough on mobile networks Interactive at 29.1 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 340 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
First Contentful Paint (3G) 9013 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minify CSS Potential savings of 2 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 41% 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 98.15% 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 154 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 1,665 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
User Timing marks and measures 15 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 250 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,850 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 207 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 337 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 3,310 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 2,680 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 8.4 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 243 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 14.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 13.2 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).
Avoid enormous network payloads Total size was 15,720 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 14.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.5 s
First Contentful Paint marks the time at which the first text or image is painted

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
Congratulations! Your description is 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

233

Local Rank: CZ / Users: 84.1% / PageViews: 80.6%

66,092

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: Thu, 05 Mar 2020 18:47:25 GMT
Server: Apache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Set-Cookie: PHPSESSID=dla5o0cbchkrbpg3dsogsf8fi4; path=/; domain=.osu.cz
Access-Control-Allow-Origin: *
Upgrade: h2
Connection: Upgrade
Strict-Transport-Security: max-age=63072000; includeSubDomains
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Expect-CT: max-age=2592000
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records