6.3 sec in total
401 ms
5.6 sec
345 ms
Welcome to cityloope.de homepage info - get ready to check Cityloope best content right away, or after learning these important things about cityloope.de
direct&friendly Bio Produkte
Visit cityloope.deWe analyzed Cityloope.de page load time and found that the first response time was 401 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cityloope.de performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value9.1 s
1/100
25%
Value10.7 s
7/100
10%
Value1,840 ms
9/100
30%
Value0.667
8/100
15%
Value10.1 s
26/100
10%
401 ms
3061 ms
208 ms
204 ms
203 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 82% of them (45 requests) were addressed to the original Cityloope.de, 11% (6 requests) were made to Google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Cityloope.de.
Page size can be reduced by 240.2 kB (27%)
885.8 kB
645.6 kB
In fact, the total size of Cityloope.de main page is 885.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 680.8 kB which makes up the majority of the site volume.
Potential reduce by 84.0 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. 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 84.0 kB or 81% of the original size.
Potential reduce by 83.3 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. Obviously, Cityloope needs image optimization as it can save up to 83.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 72.8 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. Cityloope.de needs all CSS files to be minified and compressed as it can save up to 72.8 kB or 87% of the original size.
Number of requests can be reduced by 31 (60%)
52
21
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cityloope. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
cityloope.de
401 ms
www.cityloope.de
3061 ms
modal.css
208 ms
layout_3col_132.css
204 ms
nav_vlist.css
203 ms
nav_shinybuttons.css
189 ms
jquery.treeview.css
209 ms
clp_pinboard.css
214 ms
master.css
282 ms
clp_menu.css
302 ms
clp_mod_bar.css
295 ms
clp_mod_banner.css
301 ms
jscss.php
489 ms
jsapi
15 ms
brand
25 ms
brand
100 ms
nav_shinybuttons.css
133 ms
base.css
180 ms
basemod.css
282 ms
content.css
194 ms
print_003.css
199 ms
print_base.css
96 ms
print_general.css
96 ms
bg.png
123 ms
facebook.gif
121 ms
hechingen_1.png
119 ms
header.png
374 ms
form_bg.jpg
123 ms
bgmenu1.png
122 ms
arrow_up_48.png
199 ms
lupesearch.gif
199 ms
icon_accordion_closed.png
200 ms
icon_accordion_clear.png
224 ms
google_48.png
212 ms
Danke.jpg
1078 ms
Foto_Mentorinnen_Sozialwerk.jpg
391 ms
Hochwasserrueckhaltebecken_beim_Killberg.jpg
407 ms
Nordic_Walking_Team_Hohenzollern-dusslingen.jpg
442 ms
Jahrgang_2014_der_Hechinger_kaufm_Berufsfachschule.jpg
457 ms
Lesung-stadtbuecherei.jpg
1491 ms
Foto_MDK-Pr%C3%BCfung_2014.jpg
588 ms
img.php
720 ms
29 ms
default+en.css
3 ms
default+en.I.js
13 ms
smiley_emoticons_eckbanner03.gif
329 ms
body.png
438 ms
start.gif
452 ms
prev.gif
540 ms
end.gif
559 ms
next.gif
571 ms
google_site_search_watermark.gif
35 ms
ga.js
29 ms
__utm.gif
11 ms
cells.png
106 ms
cityloope.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
cityloope.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cityloope.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use 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 Cityloope.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 Cityloope.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.
cityloope.de
Open Graph description is not detected on the main page of Cityloope. 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: