6.5 sec in total
987 ms
5.2 sec
346 ms
Welcome to indoorline.com homepage info - get ready to check INDOORLINE best content for Italy right away, or after learning these important things about indoorline.com
Dal 1999. Tutto per la coltivazione indoor e outdoor. Spediamo in tutta Italia e in Europa
Visit indoorline.comWe analyzed Indoorline.com page load time and found that the first response time was 987 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
indoorline.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value13.3 s
0/100
25%
Value11.0 s
6/100
10%
Value2,300 ms
5/100
30%
Value0.078
95/100
15%
Value16.3 s
5/100
10%
987 ms
377 ms
384 ms
385 ms
386 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 97% of them (77 requests) were addressed to the original Indoorline.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Indoorline.com.
Page size can be reduced by 742.4 kB (45%)
1.7 MB
925.1 kB
In fact, the total size of Indoorline.com main page is 1.7 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. Images take 758.3 kB which makes up the majority of the site volume.
Potential reduce by 137.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 47.9 kB, which is 30% 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 137.3 kB or 87% of the original size.
Potential reduce by 36.7 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. INDOORLINE images are well optimized though.
Potential reduce by 441.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 441.6 kB or 74% of the original size.
Potential reduce by 126.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. Indoorline.com needs all CSS files to be minified and compressed as it can save up to 126.7 kB or 82% of the original size.
Number of requests can be reduced by 37 (47%)
78
41
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INDOORLINE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
indoorline.com
987 ms
jquery-ui.css
377 ms
default.css
384 ms
nivo-slider.css
385 ms
jquery.fancybox.css
386 ms
select-cstyle.css
389 ms
quickzoom.css
387 ms
style.css
568 ms
main.css
575 ms
style.css
573 ms
jquery.js
807 ms
jquery-ui.js
968 ms
jquery.mousewheel.pack.js
576 ms
jquery.marquee.js
756 ms
jquery.accordion.js
762 ms
jquery.form.js
765 ms
jquery.nivo.slider.pack.js
767 ms
jquery.fancybox.js
948 ms
jquery.fancybox-media.js
954 ms
jquery.select-cstyle.js
956 ms
jquery.accordion2.js
960 ms
functions.js
995 ms
script.js
1138 ms
jquery.debug.js
1144 ms
jquery.placeholder.js
1145 ms
jquery.easing.js
1152 ms
jquery.pwdstr.js
1155 ms
jquery.quickzoom.js
1186 ms
script.js
1328 ms
cookiechoices.css
1158 ms
cookiechoices.js
1160 ms
reset.min.css
776 ms
gradient.gif
191 ms
wrapper-bg.png
192 ms
gradienttrasparent.gif
193 ms
header-bg-trasparent.png
191 ms
loader-small.gif
194 ms
indoorline-logo.png
193 ms
indoorlinepoint-logo.png
350 ms
loading.gif
364 ms
index.php
380 ms
index.php
771 ms
index.php
631 ms
index.php
599 ms
index.php
930 ms
index.php
761 ms
index.php
581 ms
index.php
787 ms
index.php
1000 ms
index.php
1031 ms
index.php
968 ms
index.php
1175 ms
index.php
1188 ms
index.php
1135 ms
index.php
1175 ms
index.php
1207 ms
index.php
1238 ms
cols-separator-gradient.png
1331 ms
bg_over.png
1337 ms
index.php
1350 ms
index.php
1363 ms
index.php
1382 ms
index.php
1413 ms
index.php
1505 ms
index.php
1545 ms
index.php
1562 ms
index.php
1573 ms
index.php
1592 ms
analytics.js
49 ms
collect
11 ms
index.php
1501 ms
index.php
1577 ms
wrapper-bg-bottom.png
1606 ms
footer-grass-bg.png
2574 ms
indoorline.com
2216 ms
arrows.png
1636 ms
bullets.png
1508 ms
ui-bg_flat_75_ffffff_40x100.png
1583 ms
style.css
196 ms
indoorline.com accessibility score
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.
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.
indoorline.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
indoorline.com SEO score
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
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indoorline.com can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Indoorline.com 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.
indoorline.com
Open Graph description is not detected on the main page of INDOORLINE. 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: