4.7 sec in total
299 ms
3.9 sec
573 ms
Visit e-hoi.de now to see the best up-to-date E Hoi content for Germany and also check out these interesting facts you probably never knew about e-hoi.de
Mehr als 9000 Kreuzfahrt-Routen ✓ DISQ Gesamtsieger Kreuzfahrt-Portale 2023 ✓ Top-Angebote aller Reedereien ✓ Last Minute Kreuzfahrt ✓ Top Kundenbewertungen ✓ Über 80000 Schiffsbewertungen ✓
Visit e-hoi.deWe analyzed E-hoi.de page load time and found that the first response time was 299 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
e-hoi.de performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.9 s
3/100
25%
Value10.2 s
9/100
10%
Value4,270 ms
1/100
30%
Value0.01
100/100
15%
Value10.5 s
23/100
10%
299 ms
1503 ms
24 ms
952 ms
577 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 13% of them (14 requests) were addressed to the original E-hoi.de, 58% (64 requests) were made to Image.e-hoi.de and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain E-hoi.de.
Page size can be reduced by 1.1 MB (44%)
2.6 MB
1.4 MB
In fact, the total size of E-hoi.de main page is 2.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 109.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 24.2 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 109.3 kB or 85% of the original size.
Potential reduce by 49.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. E Hoi images are well optimized though.
Potential reduce by 199.6 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 199.6 kB or 62% of the original size.
Potential reduce by 774.7 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. E-hoi.de needs all CSS files to be minified and compressed as it can save up to 774.7 kB or 65% of the original size.
Number of requests can be reduced by 26 (27%)
98
72
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Hoi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
e-hoi.de
299 ms
www.e-hoi.de
1503 ms
css
24 ms
style.css
952 ms
Royal-Caribbean1.jpg
577 ms
e-hoi-logo_101.png
246 ms
teaser_1.jpg
491 ms
hinundwegKatalog.jpg
573 ms
BannerSDM2.jpg
595 ms
flyandcruise.jpg
608 ms
ehoi_aktuell.jpg
589 ms
reederei_120w_e-hoi_hinundweg.png
271 ms
reederei_120w_e-hoi_black.png
395 ms
aida-neu.png
506 ms
MSCKreuzfahrten.png
607 ms
rci.png
619 ms
reederei_120w_celebrity.png
684 ms
reederei_120w_tui-cruises_mein-schiff.png
721 ms
reederei_120w_norwegian-cruise-line.png
706 ms
reederei_60h_costa.png
758 ms
Disney.png
733 ms
hollandamericaline.png
728 ms
reederei_120w_cunard-line.png
795 ms
Princess-neu.png
815 ms
reederei_120w_sea-cloud-cruises.png
978 ms
reederei_120w_silversea.png
840 ms
hapag-lloyd-cruises.png
976 ms
reederei_120w_regent-seven-seas-cruises.png
980 ms
reederei_120w_seabourn.png
982 ms
azamara.png
982 ms
reederei_120w_ponant.png
983 ms
reederei_120w_oceania-cruises.png
1012 ms
reederei_120w_carnival.png
1012 ms
reederei_120w_seatravel.png
1050 ms
reederei_120w_phoenix-reisen.png
1193 ms
reederei_120w_plantours-kreuzfahrten.png
1194 ms
reederei_120w_fti.png
1196 ms
reederei_120w_arosa.png
1256 ms
reederei_120w_dcs.png
1255 ms
reederei_120w_dertour.png
1252 ms
reederei_60h_colorline.png
1256 ms
China_Peking.jpg
1301 ms
js
98 ms
player_api
85 ms
script.js
688 ms
api.js
55 ms
reederei_120w_royal-caribbean.png
992 ms
AIDA7.jpg
949 ms
Mein-Schiff.jpg
890 ms
AIDA-Cruises.png
861 ms
AIDAprima1.jpg
773 ms
Costa.png
757 ms
costa_fascinosa_schiff5_8826.jpg
860 ms
reederei_30h_azamara.png
860 ms
AZA_Journey_schiff4_1869.jpg
861 ms
MSCKreuzfahrten.png
855 ms
MSC_Splendida-Schiff-front_6588.jpg
825 ms
310.jpg
810 ms
243.jpg
842 ms
276.jpg
872 ms
395.jpg
860 ms
372.jpg
860 ms
136.jpg
846 ms
305.jpg
843 ms
401.jpg
844 ms
bg.png
353 ms
de.svg
351 ms
gb.svg
288 ms
fr.svg
352 ms
es.svg
354 ms
it.svg
351 ms
ru.svg
349 ms
471.jpg
736 ms
144.jpg
747 ms
232.jpg
786 ms
307.jpg
797 ms
498.jpg
807 ms
sVvvcJDRTINJla2R4XwPVevvDin1pK8aKteLpeZ5c0A.ttf
67 ms
OsJ2DjdpjqFRVUSto6IffCZ2oysoEQEeKwjgmXLRnTc.ttf
210 ms
_aijTyevf54tkVDLy-dlnCZ2oysoEQEeKwjgmXLRnTc.ttf
212 ms
0ihfXUL2emPh0ROJezvraCZ2oysoEQEeKwjgmXLRnTc.ttf
212 ms
e.ttf
413 ms
537.jpg
827 ms
www-widgetapi.js
210 ms
274.jpg
825 ms
gtm.js
148 ms
434.jpg
801 ms
387.jpg
849 ms
recaptcha__en.js
210 ms
analytics.js
30 ms
conversion_async.js
21 ms
ld.js
18 ms
fallback
34 ms
29 ms
event
22 ms
linkid.js
11 ms
collect
12 ms
collect
102 ms
event
194 ms
fallback__ltr.css
28 ms
payload
26 ms
51 ms
css
86 ms
ga-audiences
27 ms
logo_48.png
12 ms
refresh.png
18 ms
audio.png
35 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
49 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
58 ms
dis.aspx
266 ms
e-hoi.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
e-hoi.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
e-hoi.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-hoi.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that E-hoi.de main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
e-hoi.de
Open Graph data is detected on the main page of E Hoi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: