2.8 sec in total
459 ms
2.2 sec
216 ms
Welcome to buzzply.com homepage info - get ready to check Buzzply best content right away, or after learning these important things about buzzply.com
"Partner with Buzzply for effective direct marketing through food delivery driver partnerships delivering custom materials."
Visit buzzply.comWe analyzed Buzzply.com page load time and found that the first response time was 459 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
buzzply.com performance score
459 ms
72 ms
147 ms
290 ms
222 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Buzzply.com, 72% (49 requests) were made to 2uzse02afdylxhe0436jpav1.wpengine.netdna-cdn.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source 2uzse02afdylxhe0436jpav1.wpengine.netdna-cdn.com.
Page size can be reduced by 546.3 kB (48%)
1.1 MB
598.4 kB
In fact, the total size of Buzzply.com main page is 1.1 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. 55% of websites need less resources to load. Images take 424.6 kB which makes up the majority of the site volume.
Potential reduce by 107.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 107.9 kB or 84% of the original size.
Potential reduce by 3.9 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. Buzzply images are well optimized though.
Potential reduce by 236.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 236.4 kB or 68% of the original size.
Potential reduce by 198.1 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. Buzzply.com needs all CSS files to be minified and compressed as it can save up to 198.1 kB or 81% of the original size.
Number of requests can be reduced by 40 (67%)
60
20
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buzzply. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
buzzply.com
459 ms
wp-emoji-release.min.js
72 ms
jquery.fancybox.min.css
147 ms
easy-social-share-buttons.css
290 ms
essb-mailform.css
222 ms
css
47 ms
esi-optinforms.css
147 ms
easy-slide-in.css
149 ms
font-awesome.min.css
217 ms
styles.css
287 ms
checkbox.min.css
293 ms
style.css
429 ms
tipsy.css
358 ms
wp-shortcode.css
359 ms
style.css
424 ms
prettyPhoto.css
435 ms
font-awesome.min.css
496 ms
responsive.css
499 ms
jquery.js
633 ms
jquery-migrate.min.js
562 ms
q2w3-fixed-widget.min.js
565 ms
placeholder.js
566 ms
easy-slide-in.js
706 ms
essbis.js
705 ms
customscript.js
701 ms
jquery.tipsy.js
703 ms
wp-shortcode.js
715 ms
css
53 ms
wp-subscribe.css
780 ms
jquery.ck.min.js
842 ms
jquery.fancybox.min.js
909 ms
jquery.placeholder.js
849 ms
ninjapopups.min.js
849 ms
essb-mailform.js
850 ms
jquery.prettyPhoto.js
979 ms
sticky.js
980 ms
ajax.js
1055 ms
history.js
1002 ms
680 ms
css
63 ms
loader.js
114 ms
nobg.png
271 ms
Buzzply_logo.png
328 ms
what-happens-when-kids-hook-thei-770x297.jpg
463 ms
d8ea4878-b6dd-49a7-8a60-4e13ea601f91_560_420-370x297.jpg
468 ms
40f0cf49-48ed-4ce6-8425-4c9622d38b6f_560_420-370x297.jpg
477 ms
99254b1c-8086-4f3b-8453-dc49fa397038_560_420-370x297.jpg
482 ms
d4c79133-6689-4b92-a21d-99025529d215_560_420-370x297.jpg
535 ms
69fe1f8e-a512-4541-9a3c-6a61b1b644c4_560_420-370x297.jpg
536 ms
e802b614-4ac5-447f-833a-c25fd401e248_560_420-370x297.jpg
743 ms
7b8c773b-abcb-429c-8165-e4f51ad1bcbe_560_420-370x297.jpg
738 ms
ad026581-6e9f-4dff-81ee-e1a3fdb98e61_560_420-370x297.jpg
684 ms
relax-surfboard-370x297.jpg
757 ms
e91d666a-2b5c-4a79-8375-fec1910836a6_560_420-370x297.jpg
740 ms
analytics.js
19 ms
fontawesome-webfont.woff
808 ms
fontawesome-webfont.woff
948 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
41 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
53 ms
collect
25 ms
collect
93 ms
impl.200-RELEASE.js
11 ms
beacon.js
46 ms
sdk.js
162 ms
133 ms
xd_arbiter.php
126 ms
xd_arbiter.php
254 ms
buzzply.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buzzply.com 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 Buzzply.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.
buzzply.com
Open Graph data is detected on the main page of Buzzply. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: