3.6 sec in total
76 ms
2.4 sec
1.1 sec
Click here to check amazing Squeaky Cheeks content for United States. Otherwise, check out these important facts you probably never knew about squeakycheeks.com
Visit squeakycheeks.comWe analyzed Squeakycheeks.com page load time and found that the first response time was 76 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
squeakycheeks.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value15.8 s
0/100
25%
Value6.0 s
47/100
10%
Value1,330 ms
17/100
30%
Value0.165
72/100
15%
Value13.2 s
12/100
10%
76 ms
990 ms
28 ms
114 ms
71 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 66% of them (69 requests) were addressed to the original Squeakycheeks.com, 6% (6 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (990 ms) belongs to the original domain Squeakycheeks.com.
Page size can be reduced by 153.9 kB (4%)
3.8 MB
3.6 MB
In fact, the total size of Squeakycheeks.com main page is 3.8 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. 80% 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.4 MB which makes up the majority of the site volume.
Potential reduce by 89.3 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 30.3 kB, which is 29% 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 89.3 kB or 85% of the original size.
Potential reduce by 20.4 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. Squeaky Cheeks images are well optimized though.
Potential reduce by 33.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 33.7 kB or 21% of the original size.
Potential reduce by 10.5 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. Squeakycheeks.com needs all CSS files to be minified and compressed as it can save up to 10.5 kB or 12% of the original size.
Number of requests can be reduced by 45 (60%)
75
30
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Squeaky Cheeks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
squeakycheeks.com
76 ms
squeakycheeks.com
990 ms
look.css
28 ms
style.css
114 ms
flexslider.css
71 ms
prod-slider.css
69 ms
simplegallery.demo2.css
66 ms
new-powdercss.css
65 ms
golden.css
67 ms
slick.min.css
79 ms
accessible-slick-theme.min.css
88 ms
active-page.css
84 ms
newpickleball2.css
81 ms
css2
111 ms
bootstrap.min.css
102 ms
jquery-3.3.1.slim.min.js
77 ms
popper.min.js
130 ms
bootstrap.min.js
148 ms
sweetalert.min.js
81 ms
font-awesome.min.css
109 ms
css
109 ms
jquery.flexslider.js
87 ms
jquery.min.js
74 ms
jquery.min.js
108 ms
common.js
108 ms
jquery.aw-showcase.js
109 ms
simplegallery.js
107 ms
jquery.cookie.js
142 ms
jquery.maskedinput-1.3.min.js
127 ms
slick.min.js
125 ms
slickSliderJs.js
141 ms
js
136 ms
email-decode.min.js
117 ms
jquery.mask.js
390 ms
css2
45 ms
css2
46 ms
css2
45 ms
obtp.js
332 ms
events.js
332 ms
fbevents.js
218 ms
gtm.js
50 ms
pixel.js
320 ms
recorder.js
311 ms
tfa.js
331 ms
sq-loader.png
33 ms
site-logo.png
33 ms
new-hero-banner.png
355 ms
gusset-individual-use-packs.png
357 ms
crazy-sec-icon.png
32 ms
crazy-sec-img.jpg
199 ms
foot01.png
198 ms
bene-mult1.jpg
199 ms
chafing.png
310 ms
bene-mult2.jpg
311 ms
foot03.png
312 ms
bene-mult3.jpg
310 ms
foot04.png
357 ms
bene-mult4.jpg
356 ms
home-module3.jpg
384 ms
30-days-money-back-guarantee.png
368 ms
squeaky-cheeks-comfort.png
379 ms
squeaky-cheeks-active.png
392 ms
1682465256squeaky-cheeks-unscented.png
386 ms
1690352188SC-Cream_front.jpg
369 ms
doc.jpg
383 ms
blue-tick.png
383 ms
footer-logo.png
430 ms
upi.png
431 ms
check-icon.jpg
413 ms
KFOmCnqEu92Fr1Me5Q.ttf
204 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
226 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
245 ms
KFOkCnqEu92Fr1MmgWxP.ttf
254 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
254 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
255 ms
Gotham-Bold_1.woff
394 ms
Gotham-Bold.woff
375 ms
Gotham-Bold_1.ttf
367 ms
Gotham-Bold.ttf
415 ms
Gotham-Medium_1.woff
416 ms
Gotham-Medium.woff
424 ms
Gotham-Black.woff
531 ms
Gotham-Medium_1.ttf
595 ms
Gotham-Medium.ttf
608 ms
Gotham-Black.ttf
566 ms
Gotham-Book.woff
595 ms
Gotham-Book.ttf
635 ms
Gotham-XLight.woff
714 ms
fontawesome-webfont.woff
120 ms
Gotham-Light_1.woff
733 ms
Gotham-Light.woff
774 ms
Gotham-Light_1.ttf
768 ms
tracking.js
140 ms
Gotham-XLight.ttf
666 ms
config
87 ms
rp.gif
84 ms
a2_ekpwzoojgast_telemetry
62 ms
Gotham-Light.ttf
719 ms
Gotham-Thin.woff
777 ms
Gotham-Thin.ttf
806 ms
main.MTcwODM0ODQ4NQ.js
57 ms
json
81 ms
cds-pips.js
22 ms
eid.es5.js
22 ms
pips.taboola.com
17 ms
squeakycheeks.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.
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 IDs are not unique
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
squeakycheeks.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
squeakycheeks.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Squeakycheeks.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 Squeakycheeks.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.
squeakycheeks.com
Open Graph description is not detected on the main page of Squeaky Cheeks. 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: