2 sec in total
405 ms
1.1 sec
462 ms
Click here to check amazing Squeeze Mybigcommerce content for United States. Otherwise, check out these important facts you probably never knew about squeeze.mybigcommerce.com
The Official Squeeze Merchandise Store
Visit squeeze.mybigcommerce.comWe analyzed Squeeze.mybigcommerce.com page load time and found that the first response time was 405 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
squeeze.mybigcommerce.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value8.1 s
2/100
25%
Value6.3 s
42/100
10%
Value2,110 ms
7/100
30%
Value0.091
92/100
15%
Value8.6 s
37/100
10%
405 ms
67 ms
70 ms
140 ms
152 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Squeeze.mybigcommerce.com, 50% (39 requests) were made to Cdn5.bigcommerce.com and 23% (18 requests) were made to Cdn6.bigcommerce.com. The less responsive or slowest element that took the longest time to load (405 ms) belongs to the original domain Squeeze.mybigcommerce.com.
Page size can be reduced by 743.1 kB (23%)
3.2 MB
2.4 MB
In fact, the total size of Squeeze.mybigcommerce.com main page is 3.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 36.5 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 36.5 kB or 81% of the original size.
Potential reduce by 154.6 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. Squeeze Mybigcommerce images are well optimized though.
Potential reduce by 310.0 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 310.0 kB or 71% of the original size.
Potential reduce by 242.0 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. Squeeze.mybigcommerce.com needs all CSS files to be minified and compressed as it can save up to 242.0 kB or 82% of the original size.
Number of requests can be reduced by 49 (65%)
75
26
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Squeeze Mybigcommerce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
squeeze.mybigcommerce.com
405 ms
font-awesome.min.css
67 ms
uniform.default.css
70 ms
css
140 ms
css
152 ms
css
156 ms
styles.css
70 ms
iselector.css
74 ms
flexslider.css
71 ms
slide-show.css
77 ms
styles-slide-show.css
76 ms
social.css
96 ms
styles.css
111 ms
responsive.css
128 ms
white.css
108 ms
hipster.css
119 ms
theme.css
127 ms
product.attributes.css
129 ms
ui.all.css
130 ms
product.quickview.css
133 ms
imodal.css
134 ms
store.css
134 ms
jquery.min.js
134 ms
menudrop.js
64 ms
jquery.masonry.js
68 ms
common.js
69 ms
iselector.js
67 ms
viewport.js
68 ms
jquery.uniform.min.js
82 ms
modernizr.js
119 ms
jquery.autobox.js
118 ms
init.js
112 ms
imagesLoaded.js
103 ms
quickview.js
109 ms
main.js
98 ms
jquery-ui.min.js
170 ms
jquery.validate.js
100 ms
product.functions.js
98 ms
product.attributes.js
101 ms
quickview.js
106 ms
quickview.initialise.js
105 ms
jquery.form.js
106 ms
imodal.js
104 ms
quicksearch.js
104 ms
jquery.flexslider.js
105 ms
bc_pinstrumentation.min.js
105 ms
jquery.bgiframe.min.js
106 ms
superfish.js
105 ms
visitor.js
98 ms
css
82 ms
analytics.min.js
28 ms
fornax.min.js
24 ms
beacon_api.js
27 ms
ajax-loader.gif
25 ms
squeeze_supemanlogo_1445270007__17840.png
111 ms
bg.jpg
22 ms
search-icon.png
84 ms
Red_Hoodie.png
95 ms
cttg_pink_packshot__29289.jpg
311 ms
Live2015_CD.jpeg
90 ms
Mens_Forgotten__36225.1454946602.356.300.png
83 ms
SqueezeTourBook__75988.1444417575.356.300.jpg
83 ms
61PgXuRanbL__15090.1443531678.356.300.jpg
90 ms
Mug__81939.1450194629.356.300.png
91 ms
Squeeze_Tour__40693.1454946639.356.300.png
89 ms
Red_Hoodie__02527.1450194301.356.300.png
100 ms
London_PS__92121.1445603073.356.300.jpg
102 ms
Hoodie__41190.1450264717.356.300.png
102 ms
61PgXuRanbL_2__30463.1443532442.356.300.jpg
102 ms
fontawesome-webfont.woff
76 ms
bg_direction_nav.png
66 ms
hero_prev.gif
72 ms
hero_next.gif
92 ms
blue-left-arrow.jpg
91 ms
submit-arrow.png
90 ms
sprite-social.png
161 ms
bc-logo.png
161 ms
index.php
140 ms
squeeze.mybigcommerce.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-hidden="true"] elements contain focusable descendents
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
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.
squeeze.mybigcommerce.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
squeeze.mybigcommerce.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Squeeze.mybigcommerce.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 Squeeze.mybigcommerce.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.
squeeze.mybigcommerce.com
Open Graph description is not detected on the main page of Squeeze Mybigcommerce. 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: