3.5 sec in total
209 ms
3 sec
248 ms
Welcome to slam.com homepage info - get ready to check SLAM best content for Italy right away, or after learning these important things about slam.com
Sail beyond the horizon with SLAM: high-quality technical sailing apparel, tested by athletes and experienced sailors.
Visit slam.comWe analyzed Slam.com page load time and found that the first response time was 209 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
slam.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value30.0 s
0/100
25%
Value21.2 s
0/100
10%
Value5,200 ms
0/100
30%
Value1.408
0/100
15%
Value40.7 s
0/100
10%
209 ms
119 ms
106 ms
106 ms
215 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 68% of them (47 requests) were addressed to the original Slam.com, 10% (7 requests) were made to Cms.nerocreativo.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (978 ms) belongs to the original domain Slam.com.
Page size can be reduced by 166.9 kB (13%)
1.3 MB
1.2 MB
In fact, the total size of Slam.com main page is 1.3 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 15.4 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.8 kB, which is 19% 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 15.4 kB or 77% of the original size.
Potential reduce by 45.8 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. SLAM images are well optimized though.
Potential reduce by 65.7 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 65.7 kB or 59% of the original size.
Potential reduce by 39.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. Slam.com needs all CSS files to be minified and compressed as it can save up to 39.9 kB or 85% of the original size.
Number of requests can be reduced by 22 (34%)
65
43
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SLAM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
en
209 ms
119 ms
stylesheet.css
106 ms
shared.css
106 ms
header-footer.css
215 ms
home.css
207 ms
config.js
210 ms
mootools-yui-compressed.js
37 ms
mootools-more-1.3.2.1.js
314 ms
swfobject.js
207 ms
spin.min.js
206 ms
maps
64 ms
shared.js
307 ms
home.js
308 ms
ceaeb3418b7a24a5027a02c7dd3d2095.jpg
609 ms
tweet_button.html
65 ms
tweet_button.html
68 ms
tweet_button.html
73 ms
6a7ad44410de9a8b2bb0bf0a46059327.jpg
515 ms
749d0ce0757aab8b1159624d1dd94e12.jpg
833 ms
d240c2100e23a622896506da39c94758.jpg
272 ms
3b2944c69f23b8c3cf317a2add035ad6.jpg
272 ms
80300c78eb430dcd11bdc087b033a69d.jpg
271 ms
dafebe04c2ba53867ac4c0bf931e5050.jpg
677 ms
logo_slam.png
144 ms
menu-item-sep.png
144 ms
header-eur.png
143 ms
facebook-header.png
143 ms
twitter-header.png
142 ms
youtube-header.png
142 ms
search-header.png
226 ms
next-product-active.png
223 ms
volume-on.png
224 ms
logo-header.png
221 ms
bg-ffffff-80.png
225 ms
background-p.jpg
221 ms
buy-now.png
317 ms
logo-footer.png
316 ms
GoogleMap.jpg
417 ms
vertical-sep-footer.png
317 ms
youtube-footer.png
318 ms
youtube-footer-hover.png
319 ms
facebook-footer.png
417 ms
facebook-footer-hover.png
418 ms
twitter-footer.png
418 ms
twitter-footer-hover.png
419 ms
catalogue.png
525 ms
catalogue-container_x3.png
518 ms
ss2015_thumb.png
519 ms
sy201415_thumb.png
519 ms
footer-tshirt.png
521 ms
reserved.png
523 ms
footer-tshirt-hover.png
620 ms
reserved-hover.png
619 ms
credits-container.png
620 ms
scozzese-design.png
622 ms
mpk.png
624 ms
ga.js
63 ms
jot
145 ms
jot
140 ms
jot
142 ms
like.php
139 ms
like.php
155 ms
like.php
145 ms
helveticaneueltstd-cn-webfont.woff
978 ms
bebasneue-webfont.woff
661 ms
__utm.gif
16 ms
vpc6VNjRPXV.js
485 ms
LVx-xkvaJ0b.png
549 ms
slam.com 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
slam.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
Browser errors were logged to the console
Page has valid source maps
slam.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slam.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Slam.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.
slam.com
Open Graph description is not detected on the main page of SLAM. 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: