fh-hannover.de Website Information

Daily Unique Visits: 5,113

Daily Page Views: 20,452

Income Per Day: $57

Estimated Value: $30,780

fh-hannover.de is registered under .DE top-level domain. Please check other sites in .DE zone.

Website fh-hannover.de is using the following name servers:

dns-2.dfn.de
dns-1.dfn.de
dns1.hs-hannover.de
deneb.dfn.de

and is probably hosted by Verein zur Foerderung eines Deutschen Forschungsnetzes e.V.. See the full list of other websites hosted by Verein zur Foerderung eines Deutschen Forschungsnetzes e.V..

The highest website fh-hannover.de position in Alexa rank database was 145162 and the lowest rank position was 995358. Current position of fh-hannover.de in Alexa rank database is 245427.

Desktop speed score of fh-hannover.de (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of fh-hannover.de (60/100) is better than the results of 3.95% of other sites and means that the page is not mobile-friendly.

Mobile speed score of fh-hannover.de (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

fh-hannover.de Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

fh-hannover.de whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain: fh-hannover.de
Status: connect

fh-hannover.de server information

Servers Location

fh-hannover.de desktop page speed rank

Last tested: 2019-01-12

Desktop Speed Medium

80/100

fh-hannover.de Desktop Speed Test Quick Summary

priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.hs-hannover.de/uploads/tx_t3jquery/jqu….x-1.8.x.js?1498757057
https://www.hs-hannover.de/fileadmin/layout/js/download.js?1501586706
https://www.hs-hannover.de/fileadmin/templates/js/…fancybox.js?1501586706
https://www.hs-hannover.de/typo3temp/javascript_8d985c2683.js?1498651170

Optimize CSS Delivery of the following:

https://www.hs-hannover.de/typo3temp/stylesheet_46fd242f3f.css?1498651170
https://www.hs-hannover.de/typo3conf/ext/fhh_tagge…content.css?1501586707
https://www.hs-hannover.de/fileadmin/templates/css/master.css?1527155681
https://www.hs-hannover.de/fileadmin/templates/css…tooltip.css?1501586706
https://www.hs-hannover.de/fileadmin/templates/css/f0.css?1527155681
https://www.hs-hannover.de/fileadmin/templates/css….custom.css?1501586706
https://www.hs-hannover.de/fileadmin/templates/css….ui.fhh.css?1501586706

priority - 8Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://piwik.it.hs-hannover.de/piwik.js (expiration not specified)
https://www.hs-hannover.de/clear.gif (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/bg-columns.gif (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/head_bg.png (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/link.gif (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/print.gif (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/quick.gif (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/search.gif (expiration not specified)
https://www.hs-hannover.de/fileadmin/templates/img/up.gif (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/1b75d603fb.jpg (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/30e015ea9a.jpg (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/59745cb068.jpg (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/941ac6a2c2.jpg (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/a4f8b96a31.png (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/b479c709e2.png (expiration not specified)
https://www.hs-hannover.de/typo3temp/pics/d82374d921.jpg (expiration not specified)

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://fh-hannover.de/
https://www.hs-hannover.de/
https://www.hs-hannover.de/start/index.html

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 8.5KiB (29% reduction).

Compressing https://www.hs-hannover.de/typo3temp/pics/b479c709e2.png could save 4.3KiB (28% reduction).
Compressing https://www.hs-hannover.de/fileadmin/templates/img/head_bg.png could save 1.9KiB (22% reduction).
Compressing https://www.hs-hannover.de/fileadmin/templates/img/link.gif could save 913B (88% reduction).
Compressing https://www.hs-hannover.de/fileadmin/templates/img/up.gif could save 882B (88% reduction).
Compressing https://www.hs-hannover.de/typo3temp/pics/59745cb068.jpg could save 532B (15% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.3KiB (31% reduction).

Minifying https://www.hs-hannover.de/fileadmin/templates/js/…fancybox.js?1501586706 could save 4.1KiB (31% reduction) after compression.
Minifying https://www.hs-hannover.de/typo3temp/javascript_8d985c2683.js?1498651170 could save 129B (22% reduction) after compression.
Minifying https://www.hs-hannover.de/fileadmin/layout/js/download.js?1501586706 could save 102B (32% reduction) after compression.

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 3.6KiB (28% reduction).

Minifying https://www.hs-hannover.de/fileadmin/templates/css….custom.css?1501586706 could save 1.5KiB (27% reduction) after compression.
Minifying https://www.hs-hannover.de/typo3temp/stylesheet_46fd242f3f.css?1498651170 could save 863B (37% reduction) after compression.
Minifying https://www.hs-hannover.de/fileadmin/templates/css/master.css?1527155681 could save 635B (20% reduction) after compression.
Minifying https://www.hs-hannover.de/fileadmin/templates/css/print.css?1501586706 could save 499B (38% reduction) after compression.
Minifying https://www.hs-hannover.de/fileadmin/templates/css/f0.css?1527155681 could save 111B (22% reduction) after compression.

fh-hannover.de Desktop Resource Breakdown

Total Resources	32
Number of Hosts	3
Static Resources	16
JavaScript Resources	5
CSS Resources	8

fh-hannover.de mobile page speed rank

Last tested: 2019-01-12

Mobile Speed Bad

62/100

fh-hannover.de Mobile Speed Test Quick Summary

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 12Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 10Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://fh-hannover.de/
https://www.hs-hannover.de/
https://www.hs-hannover.de/start/index.html

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 8.5KiB (29% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.3KiB (31% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 3.6KiB (28% reduction).

fh-hannover.de Mobile Resource Breakdown

Total Resources	32
Number of Hosts	3
Static Resources	16
JavaScript Resources	5
CSS Resources	8

fh-hannover.de mobile page usability

Last tested: 2019-01-12

Mobile Usability Bad

60/100

fh-hannover.de Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Die Hochschule and 6 others render only 5 pixels tall (12 CSS pixels).

Datenschutz and 3 others render only 5 pixels tall (12 CSS pixels).

Hochschule Hannover renders only 5 pixels tall (14 CSS pixels).

Fakultäten der Hochschule and 1 others render only 5 pixels tall (12 CSS pixels).

Studieren mit…her Erkrankung and 15 others render only 5 pixels tall (12 CSS pixels).

/ and 1 others render only 3 pixels tall (9 CSS pixels).

Start and 1 others render only 3 pixels tall (9 CSS pixels).

Hochschule Hannover (HsH) and 1 others render only 6 pixels tall (16 CSS pixels).

Bundesminister…telherstellung and 6 others render only 5 pixels tall (12 CSS pixels).

Das Gender-Net…chsen (LAGEN). and 5 others render only 5 pixels tall (12 CSS pixels).

mehr and 5 others render only 5 pixels tall (12 CSS pixels).

© Dr. Petra-Kristin Bonitz and 2 others render only 4 pixels tall (11 CSS pixels).

Meldungsarchiv renders only 5 pixels tall (12 CSS pixels).

Öffentlichkeit…und Marketing renders only 4 pixels tall (11 CSS pixels).

10.01.2019 renders only 4 pixels tall (11 CSS pixels).

Quicklinks renders only 5 pixels tall (12 CSS pixels).

Integriertes C…-System (iCMS) and 7 others render only 5 pixels tall (12 CSS pixels).

Veranstaltungen renders only 5 pixels tall (12 CSS pixels).

19.10.2018 and 19 others render only 5 pixels tall (12 CSS pixels).

- 18.1.2019 and 6 others render only 5 pixels tall (12 CSS pixels).

Start Lehrgang…chmann Level D and 19 others render only 5 pixels tall (12 CSS pixels).

Diese Webseite…Sie in unserer renders only 5 pixels tall (12 CSS pixels).

Datenschutzerklärung renders only 5 pixels tall (12 CSS pixels).

Einverstanden renders only 4 pixels tall (11 CSS pixels).

priority - 18Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="die-hochschule/index.html" class="hmenu">Die Hochschule</a> and 2 others are close to other tap targets.

The tap target <a href="kontakt/index.html">Kontakt</a> and 3 others are close to other tap targets.

The tap target <a href="/">Hochschule Hannover</a> is close to 1 other tap targets.

The tap target <a href="studierendenportal/index.html" class="menu">Studierende</a> and 15 others are close to other tap targets.

The tap target <a href="start/index.html">HsH</a> and 1 others are close to other tap targets.

The tap target <input type="text" name="tx_indexedsearch[sword]" class="formular"> is close to 1 other tap targets.

The tap target <input type="image" name="goButton" class="formular"> is close to 1 other tap targets.

The tap target <a href="oem/quicklinks…hop/index.html">HsH-Shop</a> and 8 others are close to other tap targets.

The tap target <a href="http://www.hs-…gen/index.html">Veranstaltungen</a> is close to 2 other tap targets.

The tap target <a href="service/verans…ver/index.html">Figürliches Ze…useum Hannover</a> and 25 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 4Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 995 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="kontakt/index.html">Kontakt</a> falls outside the viewport.
The element <a href="sitemap/index.html">Sitemap</a> falls outside the viewport.
The element <a href="impressum/index.html">Impressum</a> falls outside the viewport.
The element <a href="datenschutzerk…ung/index.html">Datenschutz</a> falls outside the viewport.
The element <div id="head_org">Hochschule Hannover</div> falls outside the viewport.
The element <form>Suchen</form> falls outside the viewport.
The element <li class="quick_spc">Quicklinks</li> falls outside the viewport.
The element <li class="quick_menu">HsH-Shop</li> falls outside the viewport.
The element <li class="quick_menu">Erstsemesterinformationen</li> falls outside the viewport.
The element <li class="quick_menu">Offene Leitbildwerkstatt</li> falls outside the viewport.
The element <li class="quick_menu">Filme über die…chule Hannover</li> falls outside the viewport.
The element <li class="quick_menu">Integriertes C…-System (iCMS)</li> falls outside the viewport.
The element <li class="quick_menu">Informationen für Flüchtlinge</li> falls outside the viewport.
The element <li class="quick_menu">Forschungscluster</li> falls outside the viewport.
The element <li class="quick_menu">Verwaltungs-Wiki</li> falls outside the viewport.
The element <h1>Veranstaltungen</h1> falls outside the viewport.
The element <li>19.10.2018 - 1…useum Hannover</li> falls outside the viewport.
The element <li>6.11.2018 - 12…sign studieren</li> falls outside the viewport.
The element <li>8.11.2018 - 24…bbrecher*innen</li> falls outside the viewport.
The element <li>15.1.2019 Ei…avi 6 (Linden)</li> falls outside the viewport.
The element <li>15.1.2019 ZL…rabendgespräch</li> falls outside the viewport.
The element <li>18.1.2019 - 20…how to: KUNST“</li> falls outside the viewport.
The element <li>19.1.2019 AB…in Hildesheim</li> falls outside the viewport.
The element <li>21.1.2019 St…chmann Level D</li> falls outside the viewport.
The element <li>22.1.2019 In…n the Trainer"</li> falls outside the viewport.
The element <a href="service/verans…ang/index.html">Nicht zu tief:…er Spaziergang</a> falls outside the viewport.
The element <li>26.1.2019 DE…DALF-Prüfungen</li> falls outside the viewport.
The element <li>31.1.2019 Wo…Schüler*innen</li> falls outside the viewport.
The element <li>5.2.2019 - 6.2…CheckMINT 2019</li> falls outside the viewport.
The element <li>5.2.2019 - 6.2…ientierungstag</li> falls outside the viewport.
The element <li>5.2.2019 Fit…die Industrie</li> falls outside the viewport.
The element <li>7.2.2019 Sti…- Präsenz *ZBS</li> falls outside the viewport.
The element <li>7.2.2019 - 8.2…Dokumentation“</li> falls outside the viewport.
The element <li>11.2.2019 Mo…den Beruf *ZBS</li> falls outside the viewport.
The element <li>12.2.2019 TestDaF</li> falls outside the viewport.
The element <li>12.2.2019 Ei…avi 6 (Linden)</li> falls outside the viewport.

fh-hannover.de HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Line: 1 Column: - 2
"...<?xml version="1..."

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 4 Column: 39 - 63
"...="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 42 Column: 1 - 51
"...nover" /> <meta http-equiv="content-language" content="de" /> <meta..."

The “scheme” attribute on the “meta” element is obsolete. Use only one scheme per field, or make the scheme declaration part of the value.

Line: 47 Column: 1 - 60
"...nover" /> <meta name="DC.Language" scheme="NISOZ39.50" content="de" /> <link..."

Bad value “schema.dc” for attribute “rel” on element “link”: The string “schema.dc” is not a registered keyword.

Line: 48 Column: 1 - 77
"...t="de" /> <link rel="schema.dc" href="http://purl.org/metadata/dublin_core_elements" /> <!--[..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 129 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/89708124c5.jpg" width="120" height="90" border="0"></td><..." Line: 140 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/e353946051.jpg" width="120" height="90" border="0"></td><..." Line: 151 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/2f4d47df4d.jpg" width="120" height="82" border="0"></td><..." Line: 162 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/84da24ec4c.png" width="120" height="67" border="0"></td><..." Line: 173 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/2de752eda0.jpg" width="120" height="90" border="0"></td><..." Line: 184 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/a4f8b96a31.png" width="120" height="85" border="0"></td><..."

No “p” element in scope but a “p” end tag seen.

Line: 133 Column: 177 - 180
"...gennehmen.</p> </d..." Line: 144 Column: 421 - 424
"...ndonesien.</p> </d..." Line: 155 Column: 332 - 335
"...ignet ist.</p> </d..." Line: 166 Column: 278 - 281
"...ubereiten.</p> </d..." Line: 177 Column: 265 - 268
"... erzählte.</p> </d..." Line: 188 Column: 224 - 227
"...d Kritik. </p> </d..."

The “clear” attribute on the “br” element is obsolete. Use CSS instead.

Line: 135 Column: 3 - 20
"... </div> <br clear="all" /> <di..." Line: 138 Column: 3 - 19
"...div> <br clear="all"/> <..." Line: 146 Column: 3 - 20
"... </div> <br clear="all" /> <di..." Line: 149 Column: 3 - 19
"...div> <br clear="all"/> <..." Line: 157 Column: 3 - 20
"... </div> <br clear="all" /> <di..." Line: 160 Column: 3 - 19
"...div> <br clear="all"/> <..." Line: 168 Column: 3 - 20
"... </div> <br clear="all" /> <di..." Line: 171 Column: 3 - 19
"...div> <br clear="all"/> <..." Line: 179 Column: 3 - 20
"... </div> <br clear="all" /> <di..." Line: 182 Column: 3 - 19
"...div> <br clear="all"/> <..." Line: 190 Column: 3 - 20
"... </div> <br clear="all" /> <di..." Line: 193 Column: 3 - 19
"...div> <br clear="all"/> ..." Line: 210 Column: 3 - 20
"..._end--> <br clear='all' /> <p ..."

Element “input” is missing required attribute “alt”.

Line: 227 Column: 5 - 109
"...x" /> <input name="goButton" class="formular" style="" type="image" src="fileadmin/templates/img/search.gif" /> </f..."

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 81 Column: 7 - 81
"...e"> <img src="clear.gif" alt="Zur Startseite" border=0 width="150" height="60"> <..." Line: 109 Column: 212 - 296
"...ex.html" ><img src="typo3temp/pics/be7cc427b1.png" width="512" height="98" border="0" alt="" /></a></..." Line: 129 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/89708124c5.jpg" width="120" height="90" border="0"></td><..." Line: 140 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/e353946051.jpg" width="120" height="90" border="0"></td><..." Line: 151 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/2f4d47df4d.jpg" width="120" height="82" border="0"></td><..." Line: 162 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/84da24ec4c.png" width="120" height="67" border="0"></td><..." Line: 173 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/2de752eda0.jpg" width="120" height="90" border="0"></td><..." Line: 184 Column: 43 - 118
"...e><tr><td><img src="typo3temp/pics/a4f8b96a31.png" width="120" height="85" border="0"></td><..."

This document appears to be written in German but the “html” start tag has “lang="en"”. Consider using “lang="de"” (or variant) instead.

Line: 5 Column: 64 - 67
"...onal.dtd"> <html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head..."

fh-hannover.de similar domains

Similar domains:

www.fh-hannover.com
www.fh-hannover.net
www.fh-hannover.org
www.fh-hannover.info
www.fh-hannover.biz
www.fh-hannover.us
www.fh-hannover.mobi
www.h-hannover.de
www.fh-hannover.de
www.ch-hannover.de
www.fch-hannover.de
www.cfh-hannover.de
www.dh-hannover.de
www.fdh-hannover.de
www.dfh-hannover.de
www.rh-hannover.de
www.frh-hannover.de
www.rfh-hannover.de
www.th-hannover.de
www.fth-hannover.de
www.tfh-hannover.de
www.gh-hannover.de
www.fgh-hannover.de
www.gfh-hannover.de
www.vh-hannover.de
www.fvh-hannover.de
www.vfh-hannover.de
www.f-hannover.de
www.fb-hannover.de
www.fhb-hannover.de
www.fbh-hannover.de
www.fg-hannover.de
www.fhg-hannover.de
www.fy-hannover.de
www.fhy-hannover.de
www.fyh-hannover.de
www.fu-hannover.de
www.fhu-hannover.de
www.fuh-hannover.de
www.fj-hannover.de
www.fhj-hannover.de
www.fjh-hannover.de
www.fn-hannover.de
www.fhn-hannover.de
www.fnh-hannover.de
www.fhhannover.de
www.fh-annover.de
www.fh-bannover.de
www.fh-hbannover.de
www.fh-bhannover.de
www.fh-gannover.de
www.fh-hgannover.de
www.fh-ghannover.de
www.fh-yannover.de
www.fh-hyannover.de
www.fh-yhannover.de
www.fh-uannover.de
www.fh-huannover.de
www.fh-uhannover.de
www.fh-jannover.de
www.fh-hjannover.de
www.fh-jhannover.de
www.fh-nannover.de
www.fh-hnannover.de
www.fh-nhannover.de
www.fh-hnnover.de
www.fh-hqnnover.de
www.fh-haqnnover.de
www.fh-hqannover.de
www.fh-hwnnover.de
www.fh-hawnnover.de
www.fh-hwannover.de
www.fh-hsnnover.de
www.fh-hasnnover.de
www.fh-hsannover.de
www.fh-hznnover.de
www.fh-haznnover.de
www.fh-hzannover.de
www.fh-hanover.de
www.fh-habnover.de
www.fh-hanbnover.de
www.fh-habnnover.de
www.fh-hahnover.de
www.fh-hanhnover.de
www.fh-hahnnover.de
www.fh-hajnover.de
www.fh-hanjnover.de
www.fh-hajnnover.de
www.fh-hamnover.de
www.fh-hanmnover.de
www.fh-hamnnover.de
www.fh-hanbover.de
www.fh-hannbover.de
www.fh-hanhover.de
www.fh-hannhover.de
www.fh-hanjover.de
www.fh-hannjover.de
www.fh-hanmover.de
www.fh-hannmover.de
www.fh-hannver.de
www.fh-hanniver.de
www.fh-hannoiver.de
www.fh-hanniover.de
www.fh-hannkver.de
www.fh-hannokver.de
www.fh-hannkover.de
www.fh-hannlver.de
www.fh-hannolver.de
www.fh-hannlover.de
www.fh-hannpver.de
www.fh-hannopver.de
www.fh-hannpover.de
www.fh-hannoer.de
www.fh-hannocer.de
www.fh-hannovcer.de
www.fh-hannocver.de
www.fh-hannofer.de
www.fh-hannovfer.de
www.fh-hannofver.de
www.fh-hannoger.de
www.fh-hannovger.de
www.fh-hannogver.de
www.fh-hannober.de
www.fh-hannovber.de
www.fh-hannobver.de
www.fh-hannovr.de
www.fh-hannovwr.de
www.fh-hannovewr.de
www.fh-hannovwer.de
www.fh-hannovsr.de
www.fh-hannovesr.de
www.fh-hannovser.de
www.fh-hannovdr.de
www.fh-hannovedr.de
www.fh-hannovder.de
www.fh-hannovrr.de
www.fh-hannoverr.de
www.fh-hannovrer.de
www.fh-hannove.de
www.fh-hannovee.de
www.fh-hannovere.de
www.fh-hannoveer.de
www.fh-hannoved.de
www.fh-hannoverd.de
www.fh-hannovef.de
www.fh-hannoverf.de
www.fh-hannovefr.de
www.fh-hannovet.de
www.fh-hannovert.de
www.fh-hannovetr.de

fh-hannover.de Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

fh-hannover.de TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

FH-HANNOVER.DE HsH - Start

fh-hannover.de Website Information

Advertisement

fh-hannover.de Alexa Rank

fh-hannover.de whois

fh-hannover.de server information

Servers Location

fh-hannover.de desktop page speed rank

fh-hannover.de Desktop Speed Test Quick Summary

priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 8Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 8.5KiB (29% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.3KiB (31% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 3.6KiB (28% reduction).

fh-hannover.de Desktop Resource Breakdown

fh-hannover.de mobile page speed rank

fh-hannover.de Mobile Speed Test Quick Summary

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 12Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 10Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 8.5KiB (29% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.3KiB (31% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 3.6KiB (28% reduction).

fh-hannover.de Mobile Resource Breakdown

fh-hannover.de mobile page usability

fh-hannover.de Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 18Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 4Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 995 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

fh-hannover.de HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

The “scheme” attribute on the “meta” element is obsolete. Use only one scheme per field, or make the scheme declaration part of the value.

Bad value “schema.dc” for attribute “rel” on element “link”: The string “schema.dc” is not a registered keyword.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

No “p” element in scope but a “p” end tag seen.

The “clear” attribute on the “br” element is obsolete. Use CSS instead.

Element “input” is missing required attribute “alt”.

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

This document appears to be written in German but the “html” start tag has “lang="en"”. Consider using “lang="de"” (or variant) instead.

fh-hannover.de similar domains

fh-hannover.de Ping