13.7 sec in total
5.5 sec
7.8 sec
468 ms
Click here to check amazing Squib content. Otherwise, check out these important facts you probably never knew about squib.ly
The domain name squib.ly is for sale. Make an offer or buy it now at a set price.
Visit squib.lyWe analyzed Squib.ly page load time and found that the first response time was 5.5 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Squib.ly rating and web reputation
squib.ly performance score
5495 ms
34 ms
66 ms
126 ms
106 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 58% of them (52 requests) were addressed to the original Squib.ly, 19% (17 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Squib.ly.
Page size can be reduced by 2.3 MB (50%)
4.6 MB
2.3 MB
In fact, the total size of Squib.ly main page is 4.6 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 34.9 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 34.9 kB or 79% of the original size.
Potential reduce by 1.2 MB
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. Obviously, Squib needs image optimization as it can save up to 1.2 MB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 417.3 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 417.3 kB or 66% of the original size.
Potential reduce by 663.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. Squib.ly needs all CSS files to be minified and compressed as it can save up to 663.9 kB or 83% of the original size.
Number of requests can be reduced by 54 (78%)
69
15
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Squib. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
squib.ly
5495 ms
analytics.js
34 ms
wp-emoji-release.min.js
66 ms
dashicons.min.css
126 ms
thickbox.css
106 ms
gravatar1.min.css
111 ms
styles.css
112 ms
video-js.css
414 ms
symple_shortcodes_styles.css
106 ms
jquery.fancybox.min.css
147 ms
wp.css
184 ms
style.min.css
178 ms
default.min.css
309 ms
jquery.js
261 ms
jquery-migrate.min.js
174 ms
jquery.noconflict.min.js
189 ms
form.js
219 ms
jquery.loadScript.min.js
225 ms
jquery.bxslider.min.js
246 ms
squibly.slider.min.js
244 ms
video.js
113 ms
videosize.min.js
263 ms
er8.me
137 ms
css
27 ms
css
38 ms
thickbox.js
279 ms
jquery.placeholder.min.js
289 ms
jquery.fancybox.pack.min.js
295 ms
validation.min.js
300 ms
comment-reply.min.js
328 ms
jquery.form.min.js
331 ms
scripts.js
345 ms
wp-embed.min.js
349 ms
menus.min.js
356 ms
tooltipster.min.js
347 ms
selectnav.min.js
372 ms
dropkick.min.js
381 ms
jquery-ui-1.10.3.custom.min.js
408 ms
jquery.sharrre-1.3.4.min.js
398 ms
jquery.reveal.min.js
397 ms
countdown.min.js
402 ms
global.min.js
423 ms
collect
12 ms
_meta.min.css
333 ms
css
15 ms
__utm.gif
98 ms
squibly_logo_web.png
262 ms
e162cbfbee927e4d125745e011b6dcff.jpg
453 ms
micro-logo.png
690 ms
iStock_000024463441Medium.jpg
816 ms
SquiblyHomepage.png
428 ms
397.png
234 ms
363.png
233 ms
Viral-Marketing.png
232 ms
303-alt.png
285 ms
136-alt.png
292 ms
242-alt.png
290 ms
342-alt.png
289 ms
264-alt.png
338 ms
302-alt.png
422 ms
163-alt.png
422 ms
238-alt.png
423 ms
c9881af5e0a5d68331d631114a42eb98.jpg
608 ms
4f777af3b2346c6fcd71efe06b7576a8.jpg
584 ms
8N2EojKhV8w
220 ms
toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
152 ms
toadOcfmlt9b38dHJxOBGHiec-hVyr2k4iOzEQsW1iE.woff
167 ms
toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
168 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
168 ms
toadOcfmlt9b38dHJxOBGNbE_oMaV8t2eFeISPpzbdE.woff
169 ms
toadOcfmlt9b38dHJxOBGMa9awK0IKUjIWABZIchFI8.woff
168 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
168 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
166 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
168 ms
fpTVHK8qsXbIeTHTrnQH6GGomRtBD2u8FwSY4jjlmeA.woff
169 ms
fpTVHK8qsXbIeTHTrnQH6PwwJPUC4r0o28cUCbhjOjM.woff
169 ms
M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
168 ms
fpTVHK8qsXbIeTHTrnQH6PULlOK_XQENnt2ryrY843E.woff
167 ms
fpTVHK8qsXbIeTHTrnQH6Nog-We9VNve39Jr4Vs_aDc.woff
168 ms
fpTVHK8qsXbIeTHTrnQH6ONg1gFYvjbPSGxSBhvPu6E.woff
168 ms
loadingAnimation.gif
204 ms
www-embed-player-vflfNyN_r.css
19 ms
www-embed-player.js
38 ms
base.js
56 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
35 ms
ad_status.js
35 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
29 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
40 ms
micro-logo.png
1106 ms
squib.ly SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Squib.ly 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 Squib.ly 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.
squib.ly
Open Graph description is not detected on the main page of Squib. 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: