BUFF.LY Social Media Management Platform | Buffer


buff.ly website information.

buff.ly domain name is registered by .LY top-level domain registry. See the other sites registred in .LY domain zone.

Following name servers are specified for buff.ly domain:

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

and probably website buff.ly is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.

According to Alexa traffic rank the highest website buff.ly position was 5039 (in the world). The lowest Alexa rank position was 998006. Now website buff.ly ranked in Alexa database as number 5205 (in the world).

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

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

Mobile speed measurement 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.

Weekly Rank Report

DateRankChange
May-02-2024 5,205-2
May-01-2024 5,20322
Apr-30-2024 5,225-19
Apr-29-2024 5,206-11
Apr-28-2024 5,19510
Apr-27-2024 5,20546
Apr-26-2024 5,251-4

Advertisement

buff.ly Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



buff.ly whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: buff.ly
Registry Domain ID: 24141-CoCCA
Registry WHOIS Server:: whois.nic.ly
Creation Date: 2012-04-28T22:00:00.0Z
Registry Expiry Date: 2024-04-28T22:00:00.0Z
Registrar Registration Expiration Date: 2024-04-28T22:00:00.0Z
Registrar: Libyan Spider Network (int)
Registrar Abuse Contact Email: support@register.ly
Registrar Abuse Contact Phone: +1.8448469791
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: GSZ1z-oQT8H
Registrant Name: Joel Gascoigne
Registrant Organization: Buffer
Registrant Street: 51 Federal St
Registrant City: San Francisco
Registrant State/Province: CA
Registrant Postal Code: 94107
Registrant Country: US
Registrant Phone: +41.59262032
Registrant Email: domains@rwgusa.com
Name Server: ns-1435.awsdns-51.org
Name Server: ns-1542.awsdns-00.co.uk
Name Server: ns-372.awsdns-46.com
Name Server: ns-766.awsdns-31.net
DNSSEC: unsigned
>>> Last update of WHOIS database: 2021-05-14T07:23:28.144Z

buff.ly server information

Servers Location

IP Address
67.199.248.13
67.199.248.12
Region
New York
New York
City
New York City
New York City

buff.ly desktop page speed rank

Last tested: 2018-11-08


Desktop Speed Medium
66/100

buff.ly Desktop Speed Test Quick Summary


priority - 18 Eliminate 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.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

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 - 18 Optimize 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 - 9 Avoid 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 - 4 Leverage 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 - 4 Enable 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 - 0 Minify 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 - 0 Minify 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 Resources

Total Resources70
Number of Hosts18
Static Resources53
JavaScript Resources15
CSS Resources6

buff.ly Desktop Resource Breakdown

buff.ly mobile page speed rank

Last tested: 2018-11-08


Mobile Speed Bad
48/100

buff.ly Mobile Speed Test Quick Summary


priority - 72 Eliminate 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.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

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 - 34 Avoid 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 - 9 Optimize 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 - 6 Leverage 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 - 0 Minify 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 - 0 Minify 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 Resources

Total Resources62
Number of Hosts18
Static Resources47
JavaScript Resources15
CSS Resources6

buff.ly Mobile Resource Breakdown

buff.ly mobile page usability

Last tested: 2018-11-08


Mobile Usability Good
99/100

buff.ly Mobile Usability Test Quick Summary


priority - 0 Size 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 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 networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


buff.ly TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.