Your Website Score is

Similar Ranking

46
CNAM - PORTAIL NATIONAL - ACCUEIL | CONSERVATOIRE NATIONAL DES ARTS ET MÉTIERS
cnam.fr
46
UNIVERSITÄT KLAGENFURT
aau.at
46
USN - UNIVERSITETET I SØRØST-NORGE
usn.no
46
HOCHSCHULE MNCHEN - HOCHSCHULE FR ANGEWANDTE WISSENSCHAFTEN MNCHEN
hm.edu
46
GDAŃSKI UNIWERSYTET MEDYCZNY: STRONA GŁÓWNA
gumed.edu.pl
46
UNIVERSITÉ LE HAVRE NORMANDIE - ULHN - UNIVERSITÉ LE HAVRE NORMANDIE
univ-lehavre.fr
46
ÓBUDAI EGYETEM: TEHETSÉG. SIKER. KÖZÖSSÉG
uni-obuda.hu

46 gumed.edu.pl Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 98%
Best Practices Desktop Score 85%
SEO Desktop Score 90%
Progressive Web App Desktop Score 54%
Performance Mobile Score 75%
Best Practices Mobile Score 77%
SEO Mobile Score 100%
Progressive Web App Mobile Score 56%
Page Authority Authority 45%
Domain Authority Domain Authority 45%
Moz Rank 4.5/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 43 Characters
GDAŃSKI UNIWERSYTET MEDYCZNY: STRONA GŁÓWNA
Meta Description 245 Characters
Serwis internetowy Gdańskiego Uniwersytetu Medycznego (GUMed). Informacje o strukturze organizacyjnej i życiu Uczelni. Studia i zasady rekrutacji. Gazeta AMG. Konferencje i wydarzenia. Informacje dla studentów i lekarzy. Kształcenie podyplomowe.
Effective URL 20 Characters
https://gumed.edu.pl
Excerpt Page content
Gdański Uniwersytet Medyczny: Strona główna na stronach GUMed w tym serwisie Szukaj ...
Keywords Cloud Density
gdański15 uniwersytet15 medyczny15 gumed10 zobacz4 uczelnia4 twitter3 youtube3 facebook3 instagram3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
gdański 15
uniwersytet 15
medyczny 15
gumed 10
zobacz 4
uczelnia 4
twitter 3
youtube 3
facebook 3
instagram 3
Google Preview Your look like this in google search result
GDAŃSKI UNIWERSYTET MEDYCZNY: STRONA GŁÓWNA
https://gumed.edu.pl
Serwis internetowy Gdańskiego Uniwersytetu Medycznego (GUMed). Informacje o strukturze organizacyjnej i życiu Uczelni. Studia i zasady rekrutacji. Gaz
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~37.53 KB
Code Size: ~24.93 KB
Text Size: ~12.6 KB Ratio: 33.57%

Estimation Traffic and Earnings

912
Unique Visits
Daily
1,687
Pages Views
Daily
$4
Income
Daily
25,536
Unique Visits
Monthly
48,080
Pages Views
Monthly
$100
Income
Monthly
295,488
Unique Visits
Yearly
566,832
Pages Views
Yearly
$1,056
Income
Yearly

Desktop

Desktop Screenshot
First CPU Idle 1.3 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,877 KB
Large network payloads cost users real money and are highly correlated with long load times
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 0.4 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 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 9 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 534 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)
Preload key requests Potential savings of 150 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 11 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 60 requests • 4,877 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 7 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.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
Remove unused CSS Potential savings of 39 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,963 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
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 190 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 2,217 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.0 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 394 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated

Mobile

Mobile Screenshot
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 51 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.3 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 3,736 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.3 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.4 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 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 9 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 534 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)
Preload key requests Potential savings of 630 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 11 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 6.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 54 requests • 3,736 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 7 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.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
First Contentful Paint (3G) 2855 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 sized appropriately 100% 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 39 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,112 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
Server response times are low (TTFB) Root document took 40 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 530 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,558 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 20 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 80 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

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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

1,742

Local Rank: PL / Users: 96.7% / PageViews: 99.1%

164,407

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
Date: Thu, 05 Mar 2020 23:03:59 GMT
Content-Type: text/html
Last-Modified: Thu, 05 Mar 2020 07:25:13 GMT
Connection: keep-alive
Vary: Accept-Encoding
ETag: W/"5e60a959-95ac"
Strict-Transport-Security: max-age=15768000
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records