4.8 sec in total
1.1 sec
2.8 sec
884 ms
Click here to check amazing Squeem content for United States. Otherwise, check out these important facts you probably never knew about squeem.net
Squeem's curve creating shapewear enhances all body types, revealing the most sensual side of you. For comfort at every curve, find out which product fits you.
Visit squeem.netWe analyzed Squeem.net page load time and found that the first response time was 1.1 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
squeem.net performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value23.8 s
0/100
25%
Value16.6 s
0/100
10%
Value13,930 ms
0/100
30%
Value0.295
40/100
15%
Value26.3 s
0/100
10%
1097 ms
38 ms
25 ms
20 ms
47 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Squeem.net, 4% (4 requests) were made to F.vimeocdn.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Squeem.com.
Page size can be reduced by 2.0 MB (37%)
5.4 MB
3.4 MB
In fact, the total size of Squeem.net main page is 5.4 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. 85% 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 45.8 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 45.8 kB or 79% of the original size.
Potential reduce by 105.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. Squeem images are well optimized though.
Potential reduce by 826.9 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 826.9 kB or 71% of the original size.
Potential reduce by 1.0 MB
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. Squeem.net needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 91% of the original size.
Number of requests can be reduced by 63 (61%)
104
41
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Squeem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.squeem.com
1097 ms
squeem.com
38 ms
stylesheet.css
25 ms
jquery-1.10.2.js
20 ms
jquery.elevatezoom.js
47 ms
jquery-ui.js
50 ms
froogaloop.js
85 ms
prettyPhoto.css
101 ms
wp-video-lightbox.css
101 ms
styles.css
104 ms
settings.css
105 ms
captions.php
703 ms
css
122 ms
style.css
185 ms
prettyPhoto.css
108 ms
superfish.css
106 ms
font-awesome.css
114 ms
audioplayer.css
109 ms
owl.carousel.css
113 ms
extend-composer.css
116 ms
orange.css
110 ms
js_composer.css
130 ms
css
121 ms
jquery.js
121 ms
jquery-migrate.min.js
117 ms
jquery.prettyPhoto.js
117 ms
video-lightbox.js
117 ms
jquery.themepunch.plugins.min.js
120 ms
jquery.themepunch.revolution.min.js
120 ms
jquery.queryloader2.js
121 ms
custom-loader.js
120 ms
modernizr.js
122 ms
jquery.parallax.js
120 ms
jquery.prettyPhoto.js
123 ms
custom-navscroll.js
122 ms
jquery.themepunch.plugins.min.js
211 ms
jquery.themepunch.revolution.min.js
209 ms
jquery.form.min.js
182 ms
scripts.js
171 ms
hoverIntent.js
205 ms
superfish.js
205 ms
smoothScroll.js
181 ms
jquery.fitvids.js
176 ms
analytics.js
100 ms
jquery.scrollTo.js
123 ms
jquery.nav.js
121 ms
retina.min.js
120 ms
owl.carousel.min.js
122 ms
comment-reply.min.js
118 ms
custom-social.js
116 ms
wp-embed.min.js
114 ms
js_composer_front.js
114 ms
wp-emoji-release.min.js
113 ms
collect
17 ms
collect
70 ms
ga-audiences
39 ms
fbevents.js
28 ms
logo.png
35 ms
nav-bg-dark.png
33 ms
curve-appeal.jpg
65 ms
banner-sexy-body.jpg
29 ms
banner-sensual-curves.jpg
93 ms
slider01.jpg
31 ms
slider02.jpg
33 ms
home-product-1.jpg
28 ms
home-product-2.jpg
31 ms
home-product-3.jpg
32 ms
home-product-4.jpg
70 ms
mairanny.jpg
61 ms
christina-defilippo.jpg
60 ms
sarah-rae.jpg
62 ms
refinery-29.jpg
65 ms
lane-bryant.jpg
64 ms
classic-shapewear.jpg
64 ms
fashion-lush.jpg
64 ms
plus-size-princess.jpg
66 ms
secret-thumb-01.jpg
67 ms
secret-thumb-02.jpg
67 ms
secret-thumb-03c.jpg
67 ms
lupa.jpg
81 ms
sm-facebook.jpg
81 ms
sm-twitter.jpg
82 ms
sm-instagram.jpg
81 ms
youtube-icon.png
84 ms
gotham-light-webfont.woff
273 ms
fontawesome-webfont.woff
273 ms
135084341
313 ms
313 ms
bg-squeem-new.jpg
304 ms
bg-80-years.jpg
256 ms
btn-player.png
303 ms
bg-shop-now.jpg
226 ms
Times%20CE%20Italic-webfont.woff
258 ms
timer.png
104 ms
secret-bg-01.jpg
106 ms
secret-bg-02.jpg
107 ms
secret-bg-03.jpg
108 ms
froogaloop2.min.js
99 ms
bullets.png
52 ms
arrow_left.png
51 ms
arrow_right.png
51 ms
gotham-book-webfont.woff
81 ms
player.js
170 ms
player.css
247 ms
ga.js
126 ms
vuid.min.js
247 ms
__utm.gif
105 ms
153408625
189 ms
proxy.html
61 ms
553694528.jpg
60 ms
__utm.gif
7 ms
collect
5 ms
squeem.net 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
squeem.net 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
Missing source maps for large first-party JavaScript
squeem.net SEO score
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 Squeem.net 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 Squeem.net 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.
squeem.net
Open Graph description is not detected on the main page of Squeem. 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: