20.3 sec in total
5.5 sec
14 sec
742 ms
Click here to check amazing Navillo content. Otherwise, check out these important facts you probably never knew about navillo.de
Visit navillo.deWe analyzed Navillo.de page load time and found that the first response time was 5.5 sec and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
navillo.de performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
5515 ms
693 ms
7 ms
30 ms
269 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Navillo.de, 66% (97 requests) were made to Navilo.es and 11% (16 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Navillo.de.
Page size can be reduced by 752.9 kB (7%)
11.0 MB
10.3 MB
In fact, the total size of Navillo.de main page is 11.0 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 10.1 MB which makes up the majority of the site volume.
Potential reduce by 89 B
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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 89 B or 32% of the original size.
Potential reduce by 90.6 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. Navillo images are well optimized though.
Potential reduce by 525.2 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 525.2 kB or 68% of the original size.
Potential reduce by 137.0 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. Navillo.de needs all CSS files to be minified and compressed as it can save up to 137.0 kB or 83% of the original size.
Number of requests can be reduced by 42 (31%)
137
95
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Navillo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
navillo.de
5515 ms
693 ms
font-awesome.css
7 ms
css
30 ms
styles.css
269 ms
front.css
279 ms
style.css
512 ms
reset.css
292 ms
bootstrap.min.css
919 ms
font-awesome.min.css
668 ms
jquery.lazyloadxt.spinner.css
411 ms
jquery.min.js
26 ms
bootstrap.min.js
549 ms
jquery.easing.min.js
19 ms
scripts.js
424 ms
main.js
540 ms
modernizr.js
558 ms
jquery.scrollTo.min.js
640 ms
jquery.form.min.js
496 ms
scripts.js
395 ms
front.js
402 ms
jquery.lazyloadxt.min.js
481 ms
jquery.lazyloadxt.extend.js
499 ms
aev-mitglied-button3.png
553 ms
men-icon.png
541 ms
logo_web.png
539 ms
fondo.jpg
1935 ms
IMG_3834-576x10241.png
548 ms
icon-01.png
539 ms
icon-05.png
540 ms
icon-04.png
544 ms
icon-03.png
545 ms
icon-02.png
546 ms
banner-scrum.jpg
925 ms
banner-agile1.jpg
948 ms
agile-infographic1.png
548 ms
banner-automotive.jpg
1374 ms
banner-international.jpg
815 ms
agile-infographic.png
814 ms
up.png
948 ms
all.png
948 ms
down.png
1150 ms
unnamed1.png
1369 ms
Screen-Shot-2014-05-30-at-12.13.02-150x150.png
1148 ms
comeet.png
1148 ms
MING_AppIcon_iPadHome_144x144.png
1370 ms
icon_152-150x150.png
1370 ms
shopnow_android_logo.png
1461 ms
App_icon_store_1024x1024.png
1373 ms
AppBounty.png
1460 ms
iphone6.png
1931 ms
IMG_2035.png
1931 ms
IMG_2036.png
1932 ms
IMG_2037.png
1930 ms
iOS-Simulator-Screen-shot-30-4May-2014-11.50.png
2737 ms
iOS-Simulator-Screen-shot-30-Maysd-2014-11.50.png
2689 ms
iOS-Simulator-Screen-shot-30-May-2014-11.50.png
2381 ms
IMG_3835.png
2252 ms
comeet_4.jpeg
2353 ms
IMG_38391.png
2225 ms
5M21SdFLkD52QavfmHs6cA.ttf
23 ms
Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf
24 ms
embed
491 ms
analytics.js
421 ms
Politica.woff
1851 ms
Politica-Bold.woff
1969 ms
OpenSans.woff
2055 ms
js
275 ms
init_embed.js
290 ms
IMG_38411.png
2000 ms
IMG_3848.png
2015 ms
locadeo1.jpg
2466 ms
locadeo2.png
2717 ms
locadeo3.png
2427 ms
samsungs6.png
2189 ms
collect
196 ms
shopnow_android_5.png
2392 ms
shopnow_android_1.png
2535 ms
shopnow_android_2.png
2084 ms
Screenshot_2014-01-10-00-03-22.png
2302 ms
Screenshot_2014-01-10-00-01-56.png
2339 ms
Screenshot_2014-01-10-00-02-20.png
2616 ms
common.js
177 ms
map.js
193 ms
google4.png
305 ms
overlay.js
303 ms
util.js
262 ms
onion.js
261 ms
search_impl.js
262 ms
StaticMapService.GetMapImage
260 ms
StaticMapService.GetMapImage
245 ms
iOS-Simulator-Screen-shot-30-May-2014-11.50.05.png
2334 ms
iOS-Simulator-Screen-shot-30-May-2014-11.57.01.png
2254 ms
iOS-Simulator-Screen-shot-30-May-2014-11.57.11.png
2267 ms
stats.js
168 ms
openhand_8_8.cur
95 ms
berlin.png
2059 ms
valencia.png
2153 ms
johannes.png
2212 ms
marjan_alias_lemmy.jpg
2297 ms
ViewportInfoService.GetViewportInfo
106 ms
ViewportInfoService.GetViewportInfo
64 ms
kh
100 ms
kh
289 ms
20150924_NaviloRetratos_0680.jpg
2098 ms
transparent.png
393 ms
20150924_NaviloRetratos_0345.jpg
2157 ms
20150924_NaviloRetratos_0042.jpg
2193 ms
controls.js
61 ms
ViewportInfoService.GetViewportInfo
380 ms
css
403 ms
entity11.png
263 ms
vt
342 ms
vt
340 ms
vt
186 ms
vt
188 ms
vt
188 ms
vt
189 ms
vt
218 ms
vt
217 ms
vt
217 ms
mapcnt6.png
117 ms
tmapctrl.png
78 ms
ViewportInfoService.GetViewportInfo
41 ms
20150924_NaviloRetratos_0551.jpg
1765 ms
20150924_NaviloRetratos_0140.jpg
1793 ms
20150924_NaviloRetratos_0608.jpg
1796 ms
20150924_NaviloRetratos_0787.jpg
1824 ms
20150924_NaviloRetratos_0137.jpg
1864 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
46 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
76 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
77 ms
AuthenticationService.Authenticate
30 ms
20150924_NaviloRetratos_0474.jpg
1544 ms
marco.jpg
1588 ms
header-bg.jpg
1653 ms
tvsmiles_background.jpg
1489 ms
comeet_header.jpg
1514 ms
nfit_ylocadeofoga.png
1642 ms
teser_locadeo_cards.jpg
1401 ms
Bildschirmfoto-2014-10-12-um-21.23.38.png
1625 ms
Background-1.png
1621 ms
fondo-bounty.jpg
2025 ms
berlin.jpg
1570 ms
valencia.jpg
1559 ms
fondo-ok.jpg
881 ms
navillo.de accessibility score
navillo.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
navillo.de SEO score
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
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Navillo.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Navillo.de main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
navillo.de
Open Graph description is not detected on the main page of Navillo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: