2.6 sec in total
452 ms
1.9 sec
152 ms
Visit intenso.de now to see the best up-to-date Intenso content for Greece and also check out these interesting facts you probably never knew about intenso.de
(Großartige Qualität. Genau auf Deinen Alltag abgestimmt.) Was Intenso ausmacht (Großartige Qualität. Genau auf Deinen Alltag abgestimmt.) Was Intenso ausmacht Deine Must-Haves. Unsere Highlights. Pow...
Visit intenso.deWe analyzed Intenso.de page load time and found that the first response time was 452 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
intenso.de performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value10.1 s
0/100
25%
Value5.6 s
53/100
10%
Value70 ms
99/100
30%
Value0.063
97/100
15%
Value7.8 s
44/100
10%
452 ms
385 ms
201 ms
396 ms
296 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 97% of them (57 requests) were addressed to the original Intenso.de, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (696 ms) belongs to the original domain Intenso.de.
Page size can be reduced by 468.1 kB (33%)
1.4 MB
943.7 kB
In fact, the total size of Intenso.de main page is 1.4 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 7.8 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 7.8 kB or 72% of the original size.
Potential reduce by 286.1 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, Intenso needs image optimization as it can save up to 286.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 149.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 149.6 kB or 69% of the original size.
Potential reduce by 24.6 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. Intenso.de needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 83% of the original size.
Number of requests can be reduced by 12 (21%)
58
46
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intenso. 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 from 5 to 1 for CSS and as a result speed up the page load time.
intenso.de
452 ms
mootools-1.2.1-core-yc.js
385 ms
mootools-1.2-more.js
201 ms
milkbox.js
396 ms
menue.js
296 ms
imageflow.js
487 ms
crawler.js
297 ms
menue.css
396 ms
styles.css
489 ms
sitemap.css
396 ms
imageflow.css
480 ms
milkbox.css
487 ms
jquery.js
681 ms
jquery.innerfade.js
489 ms
ga.js
28 ms
__utm.gif
12 ms
bg_site.jpg
100 ms
Memory_Space.jpg
200 ms
Powerbanks.jpg
201 ms
Memory_Safe.jpg
304 ms
1266489016.jpg
110 ms
1282229418.jpg
210 ms
1254837419.jpg
198 ms
1383062784.jpg
209 ms
1256117234.jpg
298 ms
1254837513.jpg
301 ms
1383061653.jpg
301 ms
1254837311.jpg
307 ms
1254483300.jpg
308 ms
1254837614.jpg
396 ms
1256032207.jpg
397 ms
1343283008.jpg
400 ms
bg_logo.jpg
401 ms
bg_flagge_ger.jpg
403 ms
bg_flagge_gb.jpg
403 ms
bg_flagge_it.jpg
490 ms
bg_flagge_fr.jpg
492 ms
bg_flagge_sp.jpg
493 ms
bg_flagge_por.jpg
497 ms
bg_flagge_pol.jpg
498 ms
bg_flagge_ru.jpg
498 ms
bg_menueBox.jpg
589 ms
bg_menueLink.jpg
590 ms
bg_suche.jpg
580 ms
bg_pfad.jpg
582 ms
bg_coverflow.jpg
667 ms
reflect3.php
571 ms
reflect3.php
659 ms
reflect3.php
661 ms
reflect3.php
663 ms
reflect3.php
670 ms
reflect3.php
671 ms
reflect3.php
696 ms
reflect3.php
688 ms
reflect3.php
603 ms
reflect3.php
607 ms
reflect3.php
607 ms
reflect3.php
599 ms
slider.png
683 ms
intenso.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 input fields do not have accessible names
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
intenso.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
intenso.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
Tap targets are not sized appropriately
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intenso.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Intenso.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.
intenso.de
Open Graph description is not detected on the main page of Intenso. 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: