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 hm.edu Last Updated: 4 months

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

Desktop

Mobile

Performance Desktop Score 97%
Best Practices Desktop Score 77%
SEO Desktop Score 100%
Progressive Web App Desktop Score 54%
Performance Mobile Score 74%
Best Practices Mobile Score 77%
SEO Mobile Score 98%
Progressive Web App Mobile Score 56%
Page Authority Authority 48%
Domain Authority Domain Authority 53%
Moz Rank 4.8/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 66 Characters
HOCHSCHULE MNCHEN - HOCHSCHULE FR ANGEWANDTE WISSENSCHAFTEN MNCHEN
Meta Description 12 Characters
Hochschule M
Effective URL 14 Characters
https://hm.edu
Meta Keywords 1 Detected
Google Preview Your look like this in google search result
HOCHSCHULE MNCHEN - HOCHSCHULE FR ANGEWANDTE WISSENSCHAFTEN
https://hm.edu
Hochschule M
Robots.txt File No Found
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~273 B
Code Size: ~256 B
Text Size: ~17 B Ratio: 6.23%

Estimation Traffic and Earnings

1,353
Unique Visits
Daily
2,503
Pages Views
Daily
$6
Income
Daily
37,884
Unique Visits
Monthly
71,336
Pages Views
Monthly
$150
Income
Monthly
438,372
Unique Visits
Yearly
841,008
Pages Views
Yearly
$1,584
Income
Yearly

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 47 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 1.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
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 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 101 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 110 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 590 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 63 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 45 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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.1 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 13 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 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.0 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 620 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.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 0.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 21 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 459 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 83 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 49 requests • 620 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.6 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 43 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 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.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 654 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.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 3.6 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 21 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 463 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 1,020 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 83 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 58 requests • 654 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 56 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 220 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.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) 7652 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 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 6 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 82% 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 72.24% 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 101 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 30 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,630 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 45 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 63 KB
Optimized images load faster and consume less cellular data

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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not 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

8,616

Local Rank: DE / Users: 52.9% / PageViews: 51.9%

95,947

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.10.3
Date: Thu, 05 Mar 2020 22:38:27 GMT
Content-Type: text/html
Content-Length: 6917
Connection: keep-alive
Last-Modified: Thu, 05 Mar 2020 00:02:43 GMT
ETag: "7c20-5a01041896ec0-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Strict-Transport-Security: max-age=15768000
Content-Language: de
DNS Records DNS Resource Records associated with a hostname
View DNS Records