Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

brokenbells.com

Home | Brokenbells

Page Load Speed

2.8 sec in total

First Response

87 ms

Resources Loaded

2.6 sec

Page Rendered

78 ms

About Website

Click here to check amazing Brokenbells content for United States. Otherwise, check out these important facts you probably never knew about brokenbells.com

The official site of Broken Bells

Visit brokenbells.com

Key Findings

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

Performance Metrics

brokenbells.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

www.brokenbells.com

87 ms

originTrials.41d7301a.bundle.min.js

43 ms

minified.js

43 ms

focus-within-polyfill.js

42 ms

polyfill.min.js

2213 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Brokenbells.com, 68% (17 requests) were made to Static.parastorage.com and 12% (3 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.8 kB (45%)

Content Size

562.1 kB

After Optimization

307.3 kB

In fact, the total size of Brokenbells.com main page is 562.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 284.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 206.5 kB

  • Original 275.4 kB
  • After minification 273.7 kB
  • After compression 68.8 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 206.5 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.8 kB
  • After minification 1.8 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. Brokenbells images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 48.2 kB

  • Original 284.9 kB
  • After minification 284.9 kB
  • After compression 236.7 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 48.2 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (67%)

Requests Now

18

After Optimization

6

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

Accessibility Review

brokenbells.com accessibility score

100

Accessibility Issues

Best Practices

brokenbells.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

brokenbells.com SEO score

100

Search Engine Optimization Advices

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 Brokenbells.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 Brokenbells.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 data is detected on the main page of Brokenbells. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: