5.9 sec in total
328 ms
4.7 sec
891 ms
Click here to check amazing SLOWEAR content for United States. Otherwise, check out these important facts you probably never knew about slowear.com
Clothing and accessories for timeless elegance. Discover our brands: Zanone, Incotex, Glanshirt, Montedoro and Officina Slowear.
Visit slowear.comWe analyzed Slowear.com page load time and found that the first response time was 328 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.
slowear.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value9.1 s
1/100
25%
Value6.6 s
38/100
10%
Value1,160 ms
22/100
30%
Value0
100/100
15%
Value13.3 s
12/100
10%
328 ms
655 ms
594 ms
147 ms
360 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 80% of them (75 requests) were addressed to the original Slowear.com, 13% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Slowear.com.
Page size can be reduced by 516.2 kB (9%)
6.0 MB
5.5 MB
In fact, the total size of Slowear.com main page is 6.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. 50% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 73.7 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 73.7 kB or 86% of the original size.
Potential reduce by 181.0 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. SLOWEAR images are well optimized though.
Potential reduce by 92.3 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 92.3 kB or 52% of the original size.
Potential reduce by 169.1 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. Slowear.com needs all CSS files to be minified and compressed as it can save up to 169.1 kB or 79% of the original size.
Number of requests can be reduced by 20 (27%)
74
54
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SLOWEAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
slowear.com
328 ms
slowear.com
655 ms
en
594 ms
loader.css
147 ms
style.css
360 ms
script.js
548 ms
carrello.css
444 ms
bluebird.min.js
27 ms
index.css
442 ms
app.js
833 ms
carrello.js
676 ms
index.js
443 ms
css
36 ms
css
49 ms
gtm.js
105 ms
logo.svg
174 ms
1px-transparent.png
176 ms
close.svg
176 ms
ico-shopping-bag.svg
262 ms
ico-favourite.svg
261 ms
ico-user.svg
264 ms
ico-incotex.svg
291 ms
ico-zanone.svg
363 ms
ico-glanshirt.svg
368 ms
ico-montedoro.svg
378 ms
400 ms
default.png
401 ms
hamburger.png
557 ms
arrow-left-submenu.svg
558 ms
arrow-right-menu-mob-black.png
559 ms
598c2b821ad01.jpg
1187 ms
598c2b7620d8a.jpg
999 ms
5980e9a25169d.jpg
741 ms
59aec56c2a127.jpg
1226 ms
5981e8e4387d0.png
585 ms
5981e8e43cb79.png
592 ms
5981e765a34ea.png
762 ms
5981e765a9441.png
697 ms
001.jpg
1011 ms
002.jpg
951 ms
003.jpg
1244 ms
004.jpg
1059 ms
005.jpg
1112 ms
006.jpg
1321 ms
ico-incotex-white.svg
1165 ms
34376842-d73a-4ba6-bdc7-3e43c3d274e2.woff
1196 ms
c2db5131-f641-4a27-963c-c1a7435d71da.woff
1235 ms
blocco-big-1.jpg
1484 ms
analytics.js
28 ms
collect
12 ms
collect
91 ms
ico-zanone-white.svg
1162 ms
blocco-small-2.jpg
1507 ms
ico-glanshirt-white.svg
1170 ms
blocco-small-3.jpg
1294 ms
W4wDsBUluyw0tK3tykhXEXYhjbSpvc47ee6xR_80Hnw.ttf
34 ms
OLffGBTaF0XFOW1gnuHF0SwlidHJgAgmTjOEEzwu1L8.ttf
39 ms
7m8l7TlFO-S3VkhHuR0atywlidHJgAgmTjOEEzwu1L8.ttf
39 ms
12mE4jfMSBTmg-81EiS-YcDdSZkkecOE1hvV7ZHvhyU.ttf
39 ms
t6Nd4cfPRhZP44Q5QAjcCywlidHJgAgmTjOEEzwu1L8.ttf
38 ms
bmC0pGMXrhphrZJmniIZpSwlidHJgAgmTjOEEzwu1L8.ttf
39 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
39 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
40 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
40 ms
Jzo62I39jc0gQRrbndN6nXYhjbSpvc47ee6xR_80Hnw.ttf
39 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
40 ms
mnpfi9pxYH-Go5UiibESIiZ2oysoEQEeKwjgmXLRnTc.ttf
40 ms
377a5ec3-4e1d-4c43-95ef-32234564c8fd.woff
1174 ms
ico-montedoro-white.svg
1172 ms
blocco-small-4.jpg
1466 ms
ico-officina-white.svg
1253 ms
blocco-small-1.jpg
2393 ms
bg-editoriale.jpg
1339 ms
scopri-slowear.jpg
1822 ms
the-store.jpg
1373 ms
collezioni-man.jpg
1392 ms
collezioni-woman.jpg
1412 ms
quick-view
1855 ms
favorites
1733 ms
scroll-top.png
1351 ms
close.svg
1335 ms
ico-shopping-bag.svg
1428 ms
ico-favourite.svg
1421 ms
ico-user.svg
1420 ms
arrow-left-submenu.svg
1387 ms
logo-white.svg
1462 ms
logo-sj-footer.svg
1293 ms
logo-sd-footer.svg
1309 ms
ico-fb-white.svg
1320 ms
ico-insta-white.svg
1297 ms
ico-tw-white.svg
1282 ms
ico-linkedin-white.svg
1254 ms
logo-sj.png
1253 ms
officina-slowear.png
1249 ms
slowear.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
slowear.com 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
Page has valid source maps
slowear.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slowear.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Slowear.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.
slowear.com
Open Graph description is not detected on the main page of SLOWEAR. 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: