Your Website Score is

Similar Ranking

44
ENPC.FR | ECOLE DES PONTS PARISTECH
enpc.fr
44
РОССИЙСКАЯ ТАМОЖЕННАЯ АКАДЕМИЯ
donrta.customs.ru
44
INICIO | UNIVERSIDADE DE VIGO
uvigo.gal
44
ERROR
glos.ac.uk
44
EMLYON BUSINESS SCHOOL : GRANDE ÉCOLE DE MANAGEMENT ET COMMERCE - ESC LYON, FRANCE - EMLYON BUSINESS SCHOOL
em-lyon.com
44
INTERNATIONAL BALKAN UNIVERSITY (IBU) - EXCELLENCE FOR THE FUTURE!
ibu.edu.mk
44
UNIVERSITY FOR TECHNOLOGY AND DESIGN | HARBOUR.SPACE BARCELONA
harbour.space

44 umb.edu.pl Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 54%
Best Practices Desktop Score 69%
SEO Desktop Score 100%
Progressive Web App Desktop Score 27%
Performance Mobile Score 20%
Best Practices Mobile Score 69%
SEO Mobile Score 96%
Progressive Web App Mobile Score 30%
Page Authority Authority 40%
Domain Authority Domain Authority 39%
Moz Rank 4.0/10
Bounce Rate Rate 0%
Title Tag 50 Characters
UNIWERSYTET MEDYCZNY W BIAŁYMSTOKU. STRONA GŁÓWNA.
Meta Description 55 Characters
Oficjalny serwis Uniwersytetu Medycznego w Białymstoku.
Effective URL 22 Characters
https://www.umb.edu.pl
Excerpt Page content
Uniwersytet Medyczny w Białymstoku. Strona główna. ...
Keywords Cloud Density
białymstoku6 medycyny6 projekty6 wydział6 zisz5 studentów5 doktorantów4 studia4 zapraszamy4 biuro4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
białymstoku 6
medycyny 6
projekty 6
wydział 6
zisz 5
studentów 5
doktorantów 4
studia 4
zapraszamy 4
biuro 4
Google Preview Your look like this in google search result
UNIWERSYTET MEDYCZNY W BIAŁYMSTOKU. STRONA GŁÓWNA.
https://www.umb.edu.pl
Oficjalny serwis Uniwersytetu Medycznego w Białymstoku.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~38.82 KB
Code Size: ~26.35 KB
Text Size: ~12.47 KB Ratio: 32.13%

Estimation Traffic and Earnings

362
Unique Visits
Daily
669
Pages Views
Daily
$0
Income
Daily
10,136
Unique Visits
Monthly
19,067
Pages Views
Monthly
$0
Income
Monthly
117,288
Unique Visits
Yearly
224,784
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 82 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 3.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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 12.9 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
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 10 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,834 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
Reduce server response times (TTFB) Root document took 1,110 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,470 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 323 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 2,166 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 30 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
Properly size images Potential savings of 822 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.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).
Avoid enormous network payloads Total size was 4,823 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.8 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 40 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 750 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 16 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 122 requests • 4,823 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
First CPU Idle 7.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 7,208 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.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 6.5 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 39 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 749 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 16 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 6.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 120 requests • 7,208 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 97 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 310 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.9 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.9 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 20 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) 13400.5 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 3 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 64% 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 99.59% 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 10 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,953 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
Reduce server response times (TTFB) Root document took 1,130 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 4,890 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 323 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 2,234 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 170 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 310 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.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
Properly size images Potential savings of 263 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 8.7 s
Speed Index shows how quickly the contents of a page are visibly populated

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
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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

0

Local Rank: / Users: / PageViews:

579,266

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: Fri, 06 Mar 2020 11:27:29 GMT
Server: Apache
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
Set-Cookie: PHPSESSID=p9immumof2tcoe5b7hclonm461; path=/
Strict-Transport-Security: max-age=15768000
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: NOSNIFF
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 20
Connection: close
Content-Type: text/html; charset=utf-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records