1.9 sec in total
233 ms
1.3 sec
386 ms
Click here to check amazing Buttonstatus content. Otherwise, check out these important facts you probably never knew about buttonstatus.com
Visit buttonstatus.comWe analyzed Buttonstatus.com page load time and found that the first response time was 233 ms and then it took 1.7 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.
buttonstatus.com performance score
233 ms
138 ms
137 ms
134 ms
132 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 70% of them (44 requests) were addressed to the original Buttonstatus.com, 14% (9 requests) were made to Ajax.googleapis.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (499 ms) belongs to the original domain Buttonstatus.com.
Page size can be reduced by 371.0 kB (31%)
1.2 MB
815.2 kB
In fact, the total size of Buttonstatus.com main page is 1.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. 60% of websites need less resources to load. Images take 714.0 kB which makes up the majority of the site volume.
Potential reduce by 30.7 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 30.7 kB or 79% of the original size.
Potential reduce by 18.3 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. Buttonstatus images are well optimized though.
Potential reduce by 141.4 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 141.4 kB or 63% of the original size.
Potential reduce by 180.7 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. Buttonstatus.com needs all CSS files to be minified and compressed as it can save up to 180.7 kB or 87% of the original size.
Number of requests can be reduced by 35 (56%)
62
27
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buttonstatus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
buttonstatus.com
233 ms
style.css
138 ms
layout.css
137 ms
styles.css
134 ms
nggallery.css
132 ms
prototype.js
12 ms
jquery.js
201 ms
scriptaculous.js
12 ms
effects.js
11 ms
lightbox.js
134 ms
jquery.cycle.all.min.js
203 ms
ngg.slideshow.min.js
201 ms
general.js
203 ms
jquery.masonry.min.js
201 ms
css
24 ms
green.css
203 ms
shortcodes.css
272 ms
custom.css
269 ms
jquery.form.min.js
267 ms
scripts.js
265 ms
add-to-cart.min.js
265 ms
jquery-plugins.min.js
268 ms
woocommerce.min.js
331 ms
animation.css
205 ms
ga.js
33 ms
builder.js
16 ms
effects.js
15 ms
dragdrop.js
19 ms
controls.js
18 ms
slider.js
20 ms
sound.js
17 ms
__utm.gif
12 ms
lightbox.css
71 ms
track
21 ms
ico-search-grad.png
110 ms
btn_donate_LG.gif
50 ms
ico-rss.png
90 ms
creepn-550x536.jpg
174 ms
dating-pink-550x513.jpg
176 ms
dating-550x533.jpg
226 ms
dont-ask-dont-tell-550x536.jpg
183 ms
DTF-550x496.jpg
228 ms
engaged-550x549.jpg
286 ms
engaged-pink-550x550.jpg
308 ms
fcuk-bullying-550x536.jpg
315 ms
heartbreaker-550x533.jpg
319 ms
in-a-relationship-pin-550x520.jpg
359 ms
In-a-Relationship-Blue-550x550.jpg
370 ms
its-complicated-550x546.jpg
417 ms
looking-for-love-pink-550x530.jpg
438 ms
looking-for-love-550x550.jpg
463 ms
player-550x547.jpg
406 ms
Single-550x545.jpg
489 ms
taken-550x535.jpg
499 ms
taken-pink-550x531.jpg
474 ms
ico-subscribe-social.png
485 ms
pixel.gif
45 ms
__utm.gif
26 ms
dropdown.png
480 ms
sprite.png
499 ms
like.php
212 ms
qeKvIRsJabD.js
137 ms
LVx-xkvaJ0b.png
152 ms
buttonstatus.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buttonstatus.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), while the claimed language is English. Our system also found out that Buttonstatus.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.
buttonstatus.com
Open Graph description is not detected on the main page of Buttonstatus. 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: