Your Website Score is

Similar Ranking

38
UNIVERZITET BIJELJINA
ubn.rs.ba
38
НОВИНИ - МІЖНАРОДНА АКАДЕМІЯ ЕКОЛОГІЇ ТА МЕДИЦИНИ
maem.kiev.ua
38
CONSERVATORIO STATALE DI MUSICA FAUSTO TORREFRANCA - VIBO VALENTIA
consvv.it
38
ÉCOLE SUPÉRIEURE D'ART DE LORRAINE — SITES DE METZ, ÉPINAL ET CEFEDEM
esalorraine.fr
38
VDU - VYTAUTO DIDŽIOJO UNIVERSITETAS
vdu.lt
38
UNIVERZITA TOMÁŠE BATI VE ZLÍNĚ | UTB
utb.cz
38
אוניברסיטת אריאל בשומרון
ariel.ac.il

38 utb.cz Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 86%
Best Practices Desktop Score 77%
SEO Desktop Score 100%
Progressive Web App Desktop Score 31%
Performance Mobile Score 41%
Best Practices Mobile Score 77%
SEO Mobile Score 98%
Progressive Web App Mobile Score 30%
Page Authority Authority 45%
Domain Authority Domain Authority 52%
Moz Rank 4.5/10
Bounce Rate Rate 0%
Title Tag 37 Characters
UNIVERZITA TOMÁŠE BATI VE ZLÍNĚ | UTB
Meta Description 147 Characters
UTB je mladá a moderní univerzita, která vzdělává 9 500 studentů v humanitních, přírodovědeckých, technických, zdravotnických a uměleckých oborech.
Effective URL 18 Characters
https://www.utb.cz
Excerpt Page content
Univerzita Tomáše Bati ve Zlíně | UTB Univerzita Tomáše Bati ve Zlíně | UTB Tomas Bata University in Zlín Search CZ Facebook Instagram Twitter Top navigationApply NowIS/STAG PortalOffice 365StudentEmployeeContact Us UTB Faculties a...
Keywords Cloud Density
faculty20 university18 centre17 study13 research10 technology8 management8 tomas7 bata7 zlín7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
faculty 20
university 18
centre 17
study 13
research 10
technology 8
management 8
tomas 7
bata 7
zlín 7
Google Preview Your look like this in google search result
UNIVERZITA TOMÁŠE BATI VE ZLÍNĚ | UTB
https://www.utb.cz
UTB je mladá a moderní univerzita, která vzdělává 9 500 studentů v humanitních, přírodovědeckých, technických, zdravotnických a uměleckých oborech.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~67.96 KB
Code Size: ~59.76 KB
Text Size: ~8.2 KB Ratio: 12.06%

Estimation Traffic and Earnings

1,482
Unique Visits
Daily
2,741
Pages Views
Daily
$6
Income
Daily
41,496
Unique Visits
Monthly
78,119
Pages Views
Monthly
$150
Income
Monthly
480,168
Unique Visits
Yearly
920,976
Pages Views
Yearly
$1,584
Income
Yearly

Desktop

Desktop Screenshot
Avoid an excessive DOM size 1,038 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 32 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 76 requests • 4,839 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 46 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 140 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 21.6 s
A fast page load over a cellular network ensures a good mobile user experience
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
Remove unused CSS Potential savings of 96 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 2,681 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
Avoid multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
Server response times are low (TTFB) Root document took 160 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 140 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 1,382 KB
Optimized images load faster and consume less cellular data
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 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.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
Speed Index 1.7 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).
Avoid enormous network payloads Total size was 4,839 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.7 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.0 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 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 7 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

Mobile

Mobile Screenshot
Serve static assets with an efficient cache policy 40 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 680 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 10.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 at 10.5 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 170 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) 6111.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 89% 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 95.52% 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 92 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 2,529 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
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Server response times are low (TTFB) Root document took 100 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,690 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 1,314 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 60 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 670 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 2.1 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
Speed Index 6.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 9.6 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 4,513 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 5.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.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 6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 7 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 934 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 32 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 4.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 71 requests • 4,513 KB
To set budgets for the quantity and size of page resources, add a budget.json file

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
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (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

394

Local Rank: CZ / Users: 84.6% / PageViews: 95.3%

84,656

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
Server: nginx/1.2.1
Date: Thu, 05 Mar 2020 19:16:33 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: mdocs-f23d4887cc59eaf5d74998a5389151af=e2370e7e5749fc123acd0bf8380610fd; path=/; secure; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Powered-By: W3 Total Cache/0.10.2
Link: ; rel="https://api.w.org/"
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records