4.6 sec in total
346 ms
3.6 sec
629 ms
Click here to check amazing 361 content for Germany. Otherwise, check out these important facts you probably never knew about 361.de
361° ist die Internet- und Werbeagentur in Leonberg. Wir beraten und planen, gestalten und formen, entwickeln und produzieren. Wir entwickeln Problemlösungen, effektive Online-Kommunikation und steige...
Visit 361.deWe analyzed 361.de page load time and found that the first response time was 346 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
361.de performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value2.3 s
93/100
25%
Value7.4 s
28/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value11.3 s
19/100
10%
346 ms
1400 ms
109 ms
324 ms
282 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 56% of them (31 requests) were addressed to the original 361.de, 22% (12 requests) were made to and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain 361.de.
Page size can be reduced by 268.1 kB (16%)
1.6 MB
1.4 MB
In fact, the total size of 361.de main page is 1.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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 23.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 3.2 kB, which is 11% 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 23.3 kB or 80% of the original size.
Potential reduce by 86 B
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. 361 images are well optimized though.
Potential reduce by 211.8 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 211.8 kB or 61% of the original size.
Potential reduce by 32.9 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. 361.de needs all CSS files to be minified and compressed as it can save up to 32.9 kB or 83% of the original size.
Number of requests can be reduced by 8 (21%)
39
31
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 361. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
361.de
346 ms
361.de
1400 ms
39b6a2c8f9c8.css
109 ms
6f12ec223dd2.js
324 ms
infobubble-compiled.js
282 ms
scripts_bcat.js
480 ms
361_bcat_custom.js
307 ms
conversion.js
42 ms
tag
215 ms
analytics.js
54 ms
arrow-right-white.png
117 ms
start-600-420-6.png
329 ms
mobile-ovisto-480-420.jpg
296 ms
start-480-420-7.jpg
312 ms
start-600-420-7.png
1503 ms
mobile-sg-740-520.jpg
518 ms
start-360-840.jpg
713 ms
mobile-pussanga-740-290.jpg
686 ms
sk-1200-840.png
783 ms
start-600-420-5.png
714 ms
mobile-set-480-420.jpg
616 ms
start-480-420-2.png
812 ms
mobile-ojs-480-420.jpg
870 ms
start-720-420.png
914 ms
mobile-pritsch-480-420.jpg
820 ms
schradi-320-420.jpg
1244 ms
mobile-schradi-480-420.jpg
902 ms
tp-600-840.jpg
923 ms
mobile-tewipack-740-290.jpg
965 ms
start-480-420-6.jpg
1090 ms
mobile-starwatch-740-290.jpg
1118 ms
1232131.png
1028 ms
collect
5 ms
collect
253 ms
vho4giy.js
422 ms
231 ms
piwik.js
664 ms
tile.png
774 ms
arrow-left-white.png
846 ms
ga-audiences
54 ms
23 ms
d
754 ms
Q1dm5cPtcG8X5DQN+0WH4D4n7DcgAAAA==
20 ms
p5BGPVfVDnvCSHo5xlIAZVA+z+MHU5P9d+4knQAKJyj6bOcz9Jw9LWaYNCrOcFazURFaRxWqyyWENuazVbuWRP6GCvzG3mwLt4V5NtIhiStinnTpAKQfF6czJdKczJpWT+KsqJq72bOP4vWYS+IaYuCnqRgGCJbrXAA==
18 ms
Q1dm5cPtcG8X5DQN+0WH4D4n7DcgAAAA==
17 ms
mDqiBmVQf0NXZuXD7XBvF+Q0DftFh+A+J+w3IAAAA=
17 ms
VtpoZ5JHvOcB41g4RCkn2wggkCC2s4OHPOYLX5niGS0c4CDxJJBIEodIJkV2SiWNdA5zhAzRN5MssjnLOVG6gAtcpJBLsveiZsWUiPaKLrWXYYwoN0GH8Pgs+73FTT9j3OE735jjF43Cs5MhmvgprN6pSBWh9vCcciqopJ4q6mjgNgMM0screujlDR8ZpYZqnGpOGAfK2X+zrWsUJX9aDLHsYz9xPirmbdnkcIzj5HKCk+SRzylOc2ZTTf+fbfV2Vqzch1kVXnWlHetX+yofztd51Q1LaQGcWsAIAAAA
15 ms
2wAA
15 ms
Q1dm5cPtcG8X5DQN+0WH4D4n7DcgAAAA==
14 ms
Y6Nf5g6ogZlUH9DV2blw+1wbxfkNA37RYfgPifsNyAAAA
12 ms
Q1dm5cPtcG8X5DQN+0WH4D4n7DcgAAAA==
11 ms
mDqiBmVQf0NXZuXD7XBvF+Q0DftFh+A+J+w3IAAAA=
10 ms
O13nVDUtpAZxawAgAAAA=
9 ms
2wAA
9 ms
p.gif
115 ms
361.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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
361.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
361.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 uses legible font sizes
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 361.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 361.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.
361.de
Open Graph description is not detected on the main page of 361. 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: