1.2 sec in total
67 ms
912 ms
249 ms
Visit slice.com now to see the best up-to-date Slice content for United States and also check out these interesting facts you probably never knew about slice.com
Shippity
Visit slice.comWe analyzed Slice.com page load time and found that the first response time was 67 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
slice.com performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value3.2 s
73/100
25%
Value1.6 s
100/100
10%
Value60 ms
100/100
30%
Value0
100/100
15%
Value3.9 s
88/100
10%
67 ms
190 ms
148 ms
89 ms
191 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Slice.com, 21% (6 requests) were made to Djcgg0wrlysb3.cloudfront.net and 10% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (278 ms) relates to the external source Api.taps.io.
Page size can be reduced by 298.0 kB (43%)
699.7 kB
401.7 kB
In fact, the total size of Slice.com main page is 699.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 410.6 kB which makes up the majority of the site volume.
Potential reduce by 50.2 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 50.2 kB or 62% of the original size.
Potential reduce by 3.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. Slice images are well optimized though.
Potential reduce by 244.2 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 244.2 kB or 59% of the original size.
Number of requests can be reduced by 12 (44%)
27
15
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
www.slice.com
67 ms
134357012.js
190 ms
tapstream.js
148 ms
event
89 ms
analytics.min.js
191 ms
hero1024.jpg
126 ms
spinner_3.gif
101 ms
features.png
99 ms
full_screens.jpg
120 ms
safety.png
99 ms
footer.png
98 ms
.gif
278 ms
event
11 ms
event
7 ms
conversion_async.js
139 ms
amplitude-2.9.0-min.gz.js
138 ms
analytics.js
123 ms
3914628.js
88 ms
localytics.js
53 ms
recorder.js
105 ms
image.gif
112 ms
visit
75 ms
collect
39 ms
collect
51 ms
51 ms
recorder_web_worker.js
31 ms
identify
25 ms
37 ms
identify
30 ms
slice.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
slice.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
slice.com SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slice.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Slice.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.
slice.com
Open Graph data is detected on the main page of Slice. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: