Tools & Wizards About Us
brokentop.org screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

brokentop.org

Broken Top Community Association - Enumerate Engage - Home

Page Load Speed

2.8 sec in total

First Response

17 ms

Resources Loaded

2.6 sec

Page Rendered

196 ms

brokentop.org screenshot

About Website

Welcome to brokentop.org homepage info - get ready to check Broken Top best content right away, or after learning these important things about brokentop.org

Enumerate Engage is the industry

Visit brokentop.org

Key Findings

We analyzed Brokentop.org page load time and found that the first response time was 17 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

brokentop.org performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

brokentop.org

17 ms

245 ms

jquery-ui.css

58 ms

jquery.fancybox.css

97 ms

css

97 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Brokentop.org, 72% (39 requests) were made to Engage.goenumerate.com and 7% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Engage.goenumerate.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.2 kB (6%)

Content Size

2.5 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brokentop.org main page is 2.5 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. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 30.9 kB

  • Original 38.7 kB
  • After minification 33.2 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 5.5 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.9 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 86.1 kB

  • Original 2.2 MB
  • After minification 2.1 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. Broken Top images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 19.5 kB

  • Original 136.7 kB
  • After minification 136.7 kB
  • After compression 117.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 19.5 kB or 14% of the original size.

CSS Optimization

-12%

Potential reduce by 13.7 kB

  • Original 110.8 kB
  • After minification 104.7 kB
  • After compression 97.1 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. Brokentop.org needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (69%)

Requests Now

51

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brokentop.org

brokentop.org

17 ms

245 ms

jquery-ui.css

jquery-ui.css

58 ms

jquery.fancybox.css

jquery.fancybox.css

97 ms

css

css

97 ms

css2

css2

104 ms

css

css

120 ms

css2

css2

120 ms

owl.carousel.css

owl.carousel.css

14 ms

perfect-scrollbar.css

perfect-scrollbar.css

40 ms

select2.min.css

select2.min.css

53 ms

dropzone.min.css

dropzone.min.css

54 ms

flatpickr.min.css

flatpickr.min.css

56 ms

theme.css

theme.css

72 ms

bootstrap_custom_engage.css

bootstrap_custom_engage.css

58 ms

bootstrap_mediaqueries_engage.css

bootstrap_mediaqueries_engage.css

58 ms

jquery-3.5.1.js

jquery-3.5.1.js

70 ms

jquery-ui.js

jquery-ui.js

70 ms

popper.min.js

popper.min.js

70 ms

bootstrap.min.js

bootstrap.min.js

101 ms

4fc9e0ed8f.js

4fc9e0ed8f.js

233 ms

stickyfill.min.js

stickyfill.min.js

70 ms

sticky-kit.min.js

sticky-kit.min.js

94 ms

is.min.js

is.min.js

95 ms

perfect-scrollbar.js

perfect-scrollbar.js

94 ms

owl.carousel.js

owl.carousel.js

95 ms

progressbar.min.js

progressbar.min.js

100 ms

select2.min.js

select2.min.js

100 ms

dropzone.min.js

dropzone.min.js

100 ms

flatpickr.min.js

flatpickr.min.js

99 ms

theme2.js

theme2.js

99 ms

jquery.fancybox.js

jquery.fancybox.js

67 ms

chart.min.js

chart.min.js

100 ms

Sortable.js

Sortable.js

159 ms

autosize.js

autosize.js

109 ms

nabrcustom.js

nabrcustom.js

110 ms

nabr.js

nabr.js

109 ms

email-decode.min.js

email-decode.min.js

99 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

89 ms

Enumerate_Engage_Logo_Knockout_RGB.png

Enumerate_Engage_Logo_Knockout_RGB.png

487 ms

EngageInAppIcon_512x512.png

EngageInAppIcon_512x512.png

459 ms

photo8_1934.jpg

photo8_1934.jpg

752 ms

photo8-1934_2.jpg

photo8-1934_2.jpg

577 ms

photo8-1934_3.jpg

photo8-1934_3.jpg

654 ms

photo8-1934_4.png

photo8-1934_4.png

729 ms

photo8-1934_5.jpg

photo8-1934_5.jpg

1126 ms

photo8-1934_6.jpg

photo8-1934_6.jpg

1252 ms

photo8-1934_7.jpg

photo8-1934_7.jpg

1254 ms

photo8-1934_8.jpg

photo8-1934_8.jpg

1318 ms

photo8-1934_9.jpg

photo8-1934_9.jpg

1386 ms

photo8-1934_10.jpg

photo8-1934_10.jpg

1456 ms

photo9_1934.png

photo9_1934.png

1502 ms

hoa_quick_access.png

hoa_quick_access.png

1735 ms

proximanova-medium-webfont.woff

proximanova-medium-webfont.woff

1209 ms

Accessibility Review

brokentop.org accessibility score

100

Accessibility Issues

Best Practices

brokentop.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

brokentop.org SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

brokentop.org

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