Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

7.8 sec in total

First Response

76 ms

Resources Loaded

6.6 sec

Page Rendered

1.1 sec

buzzlie.com screenshot

About Website

Visit buzzlie.com now to see the best up-to-date Buzzlie content for United States and also check out these interesting facts you probably never knew about buzzlie.com

Visit buzzlie.com

Key Findings

We analyzed Buzzlie.com page load time and found that the first response time was 76 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

buzzlie.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.8 s

100/100

10%

Network Requests Diagram

buzzlie.com

76 ms

amzn_ads.js

14 ms

advertisement.js

190 ms

buildv65.min.js

201 ms

widget.css

42 ms

Our browser made a total of 401 requests to load all elements on the main page. We found that 1% of them (4 requests) were addressed to the original Buzzlie.com, 60% (242 requests) were made to Cdn.buzzlie.com and 11% (45 requests) were made to Static.buzzlie.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Staticxx.facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (6%)

Content Size

39.3 MB

After Optimization

36.8 MB

In fact, the total size of Buzzlie.com main page is 39.3 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. Only a small number of websites need less resources to load. Images take 37.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 229.5 kB

  • Original 276.5 kB
  • After minification 276.2 kB
  • After compression 47.0 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 229.5 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 850.0 kB

  • Original 37.1 MB
  • After minification 36.3 MB

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. Buzzlie images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 684.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 367.2 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 684.9 kB or 65% of the original size.

CSS Optimization

-87%

Potential reduce by 696.2 kB

  • Original 803.0 kB
  • After minification 779.9 kB
  • After compression 106.8 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. Buzzlie.com needs all CSS files to be minified and compressed as it can save up to 696.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 100 (27%)

Requests Now

368

After Optimization

268

The browser has sent 368 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buzzlie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

buzzlie.com accessibility score

63

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

buzzlie.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

buzzlie.com SEO score

55

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buzzlie.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 Buzzlie.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Buzzlie. 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: