BUFF.LY Buffer | Social Media Management Software for Growing Brands

buff.ly Website Information

Daily Unique Visits: 291,482

Daily Page Views: 2,331,856

Income Per Day: $2,332

Estimated Value: $2,518,560

This website is located in United States and is using following IP address 67.199.248.13. See the complete list of popular websites hosted in United States.

buff.ly is registered under .LY top-level domain. Please check other sites in .LY zone.

Website buff.ly is using the following name servers:

  • ns-1435.awsdns-51.org
  • ns-1542.awsdns-00.co.uk
  • ns-372.awsdns-46.com
  • ns-766.awsdns-31.net

and is probably hosted by GOOGLE-PRIVATE-CLOUD - Google LLC, US. See the full list of other websites hosted by GOOGLE-PRIVATE-CLOUD - Google LLC, US.

The highest website buff.ly position in Alexa rank database was 5039 and the lowest rank position was 998006. Current position of buff.ly in Alexa rank database is 5228.

Desktop speed score of buff.ly (66/100) is better than the results of 44.37% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of buff.ly (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of buff.ly (48/100) is better than the results of 30.32% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

buff.ly Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


buff.ly whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: buff.ly
Domain Status: No Object Found
Notes: This server is not authoritative for the TLD
>>> Last update of WHOIS database: 2024-09-28T14:37:29.659Z

buff.ly server information

Servers Location

buff.ly desktop page speed rank

Last tested: 2018-11-08


Desktop Speed Medium
66/100

buff.ly Desktop Speed Test Quick Summary


priority - 18Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700
https://fonts.googleapis.com/css?family=Roboto:400,500,700,900
https://static.buffer.com/marketing/public/css/sty…0bfc39d7d363a87d24.css
https://icons.buffer.com/0.15.1/buffer-icons.css
https://static.buffer.com/marketing/public/css/fon…fc6364037d3ba53423.css
https://static.buffer.com/marketing/public/css/new…5cf556dc8c560fde52.css
https://icons.buffer.com/0.15.1/buffer-icons.css

priority - 18Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 175.7KiB (72% reduction).

Compressing and resizing https://static.buffer.com/marketing/public/img/ill…mobile-extensions1.jpg could save 74.6KiB (79% reduction).
Compressing and resizing https://static.buffer.com/marketing/public/img/ill…l-media-analytics1.jpg could save 34.3KiB (67% reduction).
Compressing and resizing https://static.buffer.com/marketing/public/img/ill…eam-collaboration1.jpg could save 33.9KiB (69% reduction).
Compressing and resizing https://static.buffer.com/marketing/public/img/ill…-media-scheduling1.jpg could save 32.8KiB (67% reduction).

priority - 9Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://buff.ly/
http://bufferapp.com/
https://buffer.com/

priority - 4Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.googletagmanager.com/gtm.js?id=GTM-58PRD29 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/152104…9171?v=2.8.33&r=stable (20 minutes)
https://fast.wistia.com/assets/external/E-v1.js (60 minutes)
https://fast.wistia.com/assets/external/allIntegrations.js (60 minutes)
https://fast.wistia.com/assets/external/externalPlayer.js (60 minutes)
https://fast.wistia.com/assets/external/popover.js (60 minutes)
https://fast.wistia.com/assets/external/wistia-mux.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 4Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 36.2KiB (71% reduction).

Compressing https://connect.facebook.net/en_US/fbevents.js could save 36.2KiB (71% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.8KiB (24% reduction).

Minifying https://static.buffer.com/marketing/public/js/part…b37c637374fb4fc0107.js could save 2.8KiB (31% reduction) after compression.
Minifying https://static.buffer.com/marketing/public/js/scri…87df40b59a19b49b459.js could save 593B (20% reduction) after compression.
Minifying https://fast.wistia.com/assets/external/allIntegrations.js could save 444B (11% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.6KiB (15% reduction).

Minifying https://buffer.com/ could save 1.4KiB (15% reduction) after compression.
Minifying https://fast.wistia.com/embed/iframe_shim?domain=com could save 119B (15% reduction) after compression.

buff.ly Desktop Resource Breakdown

Total Resources70
Number of Hosts18
Static Resources53
JavaScript Resources15
CSS Resources6

buff.ly mobile page speed rank

Last tested: 2018-11-08


Mobile Speed Bad
48/100

buff.ly Mobile Speed Test Quick Summary


priority - 72Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700
https://fonts.googleapis.com/css?family=Roboto:400,500,700,900
https://static.buffer.com/marketing/public/css/sty…0bfc39d7d363a87d24.css
https://icons.buffer.com/0.15.1/buffer-icons.css
https://static.buffer.com/marketing/public/css/fon…fc6364037d3ba53423.css
https://static.buffer.com/marketing/public/css/new…5cf556dc8c560fde52.css
https://icons.buffer.com/0.15.1/buffer-icons.css

priority - 34Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://buff.ly/
http://bufferapp.com/
https://buffer.com/

priority - 9Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 86.4KiB (91% reduction).

Compressing and resizing https://static.buffer.com/marketing/public/img/ill…mobile-extensions1.jpg could save 85.3KiB (91% reduction).
Compressing https://fast.wistia.com/assets/images/blank.gif could save 1.1KiB (90% reduction).

priority - 6Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.googletagmanager.com/gtm.js?id=GTM-58PRD29 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/152104…9171?v=2.8.33&r=stable (20 minutes)
https://fast.wistia.com/assets/external/E-v1.js (60 minutes)
https://fast.wistia.com/assets/external/allIntegrations.js (60 minutes)
https://fast.wistia.com/assets/external/engines/manual_quality_video.js (60 minutes)
https://fast.wistia.com/assets/external/popover.js (60 minutes)
https://fast.wistia.com/assets/external/wistia-mux.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 3.8KiB (24% reduction).

Minifying https://static.buffer.com/marketing/public/js/part…b37c637374fb4fc0107.js could save 2.8KiB (31% reduction) after compression.
Minifying https://static.buffer.com/marketing/public/js/scri…87df40b59a19b49b459.js could save 593B (20% reduction) after compression.
Minifying https://fast.wistia.com/assets/external/allIntegrations.js could save 444B (11% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.6KiB (15% reduction).

Minifying https://buffer.com/ could save 1.4KiB (15% reduction) after compression.
Minifying https://fast.wistia.com/embed/iframe_shim?domain=com could save 119B (15% reduction) after compression.

buff.ly Mobile Resource Breakdown

Total Resources62
Number of Hosts18
Static Resources47
JavaScript Resources15
CSS Resources6

buff.ly mobile page usability

Last tested: 2018-11-08


Mobile Usability Good
99/100

buff.ly Mobile Usability Test Quick Summary


priority - 0Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <button type="button" class="slick-prev slick-arrow">Previous</button> and 1 others are close to other tap targets.

buff.ly HTML validation

Errors

Bad value “opera-webstore-item” for attribute “rel” on element “link”: The string “opera-webstore-item” is not a registered keyword.

Line: 24 Column: 5 - 100
"...bhh"> <link rel="opera-webstore-item" href="https://addons.opera.com/en/extensions/details/buffer-2/"> <..."

End tag “header” seen, but there were open elements.

Line: 381 Column: 5 - 13
".../div> </header> ..."

Unclosed element “div”.

Line: 57 Column: 13 - 43
"... <div class="header__container"> ..." Line: 799 Column: 4 - 20
"...tion"> <div class="row"> <..."

Saw “<” when expecting an attribute name. Probable cause: Missing “>” immediately before.

Line: 847 Column: - 5
"...obile.jpg" </div> </div..."

A slash was not immediately followed by “>”.

Line: 847 Column: - 7
"...ile.jpg" </div> </div> ..."

Attribute “<” not allowed on element “img” at this point.

Line: 847 Column: 6 - 10
"...> <img class="cs-grid--mobile" src="https://static.buffer.com/marketing/public/img/customer-support/customer-support-mobile.jpg" </div> </..."

Attribute “div” not allowed on element “img” at this point.

Line: 847 Column: 6 - 10
"...> <img class="cs-grid--mobile" src="https://static.buffer.com/marketing/public/img/customer-support/customer-support-mobile.jpg" </div> </..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 847 Column: 6 - 10
"...> <img class="cs-grid--mobile" src="https://static.buffer.com/marketing/public/img/customer-support/customer-support-mobile.jpg" </div> </..." Line: 1114 Column: 15 - 6
"...<noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1521042244879171&ev=PageView&noscript=1" /></..."

End tag “section” seen, but there were open elements.

Line: 849 Column: 3 - 12
"... </div> </section> ..."

Bad value “” for attribute “src” on element “iframe”: Must be non-empty.

Line: 1060 Column: 9 - 59
"...> <iframe src class="js-modal-content modal-content"></ifra..."

Warnings

Attribute “<” is not serializable as XML 1.0.

Line: 847 Column: 6 - 10
"...> <img class="cs-grid--mobile" src="https://static.buffer.com/marketing/public/img/customer-support/customer-support-mobile.jpg" </div> </..."

Attribute “src” without an explicit value seen. The attribute may be dropped by IE7.

Line: 1060 Column: - 21
"... <iframe src class="js-modal..."

buff.ly similar domains

Similar domains:
www.buff.com
www.buff.net
www.buff.org
www.buff.info
www.buff.biz
www.buff.us
www.buff.mobi
www.uff.ly
www.buff.ly
www.vuff.ly
www.bvuff.ly
www.vbuff.ly
www.guff.ly
www.bguff.ly
www.gbuff.ly
www.huff.ly
www.bhuff.ly
www.hbuff.ly
www.nuff.ly
www.bnuff.ly
www.nbuff.ly
www.bff.ly
www.byff.ly
www.buyff.ly
www.byuff.ly
www.bhff.ly
www.buhff.ly
www.bjff.ly
www.bujff.ly
www.bjuff.ly
www.biff.ly
www.buiff.ly
www.biuff.ly
www.buf.ly
www.bucf.ly
www.bufcf.ly
www.bucff.ly
www.budf.ly
www.bufdf.ly
www.budff.ly
www.burf.ly
www.bufrf.ly
www.burff.ly
www.butf.ly
www.buftf.ly
www.butff.ly
www.bugf.ly
www.bufgf.ly
www.bugff.ly
www.buvf.ly
www.bufvf.ly
www.buvff.ly
www.bufc.ly
www.buffc.ly
www.bufd.ly
www.buffd.ly
www.bufr.ly
www.buffr.ly
www.buft.ly
www.bufft.ly
www.bufg.ly
www.buffg.ly
www.bufv.ly
www.buffv.ly

buff.ly Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


buff.ly TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.