1.5 sec in total
10 ms
986 ms
502 ms
Visit buff.ly now to see the best up-to-date Buff content for Japan and also check out these interesting facts you probably never knew about buff.ly
Use Buffer to manage your social media so that you have more time for your business. Join 160,000+ small businesses today.
Visit buff.lyWe analyzed Buff.ly page load time and found that the first response time was 10 ms and then it took 1.5 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.
buff.ly performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.8 s
54/100
25%
Value3.1 s
93/100
10%
Value1,210 ms
20/100
30%
Value0.004
100/100
15%
Value11.3 s
19/100
10%
10 ms
85 ms
105 ms
119 ms
125 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Buff.ly, 13% (7 requests) were made to Buffer.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (410 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.3 MB (51%)
2.6 MB
1.3 MB
In fact, the total size of Buff.ly main page is 2.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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 65.4 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 65.4 kB or 71% of the original size.
Potential reduce by 171.0 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. Obviously, Buff needs image optimization as it can save up to 171.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 717.6 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 717.6 kB or 66% of the original size.
Potential reduce by 370.2 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. Buff.ly needs all CSS files to be minified and compressed as it can save up to 370.2 kB or 84% of the original size.
Number of requests can be reduced by 18 (38%)
47
29
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
bufferapp.com
10 ms
buffer.com
85 ms
css
105 ms
css
119 ms
homepage.af11beb8d2897cdba7007a47c7a4c5bc.gz.css
125 ms
webfonts_bundle.0c901bab6211068beeeedc32e2ba57a9.gz.css
107 ms
jquery.min.js
108 ms
jquery-ui.min.js
146 ms
base.min.a785033f1d469fbce94f3e5cb5f5d4fa.js
109 ms
oct.js
81 ms
homepage_bundle.0bf94560864fe66adf39d8a108cb6ac1.gz.js
114 ms
jsapi
98 ms
addthis_widget.js
101 ms
buffermetrics.min.5cf5e1d04e5f254e2c93148a60999518.js
102 ms
bugsnag-2.min.js
101 ms
css
21 ms
adsct
329 ms
adsct
327 ms
fbds.js
368 ms
analytics.js
323 ms
buffer-logo@2x.png
62 ms
img-buffer-illustration-hub-960@2x.png
290 ms
ic_arrow_right_grey.svg
255 ms
ic_arrow_right.svg
257 ms
product-screenshot-queue.png
260 ms
product-screenshot-composer.png
284 ms
img_buffer_discover.png
290 ms
img_buffer_pablo.png
349 ms
img_buffer_pablo_image.png
351 ms
icon-twitter.svg
290 ms
icon-facebook.svg
289 ms
icon-linkedin.svg
298 ms
icon-google-plus.svg
297 ms
icon-pinterest.svg
295 ms
buffer-logo.png
297 ms
img-buffer-illustration-hub-320@2x.png
261 ms
ic_buffer.svg
257 ms
ic_android.svg
259 ms
ic_apple.svg
258 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
347 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
385 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
410 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
410 ms
ss-social-regular.woff
287 ms
api.html
198 ms
aquant.js
212 ms
138 ms
300lo.json
128 ms
d9G.js
230 ms
sh.7c7179124ea24ac6ba46caac.html
103 ms
178 ms
collect
100 ms
pixel;r=1032251640;a=p-rw_1uEX-gMkjA;orderid=;revenue=;labels=_fp.event.Homepage;fpan=1;fpa=P0-892469038-1456805202368;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456805202367;tzo=-180;ref=;url=https%3A%2F%2Fbuffer.com%2F;ogl=title.Buffer%20-%20A%20Smarter%20Way%20to%20Share%20on%20Social%20Media%2Cimage.http%3A%2F%2Fstatic%252Ebufferapp%252Ecom%2Fimages%2Ffacebook%2Fbuffer-logo-facebook-preview%252Epng%2Cdescription.Buffer%20makes%20it%20super%20easy%20to%20share%20any%20page%20you're%20reading%252E%20Keep%20your%20Buffer%20to
48 ms
nr-852.min.js
46 ms
buff.ly 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
buff.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
buff.ly SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buff.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 Buff.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.
buff.ly
Open Graph data is detected on the main page of Buff. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: