Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

member.buzz

Manage your Members, Create Events, and More - Member.buzz

Page Load Speed

4.7 sec in total

First Response

64 ms

Resources Loaded

2.1 sec

Page Rendered

2.5 sec

member.buzz screenshot

About Website

Visit member.buzz now to see the best up-to-date Member content and also check out these interesting facts you probably never knew about member.buzz

Member.buzz is a free platform to coordinate members, plan events, send invoices, create newsletters, collect donations, and much more.

Visit member.buzz

Key Findings

We analyzed Member.buzz page load time and found that the first response time was 64 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

member.buzz performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value2,140 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

member.buzz

64 ms

www.member.buzz

334 ms

space.min.css

59 ms

navbox.min.css

57 ms

styles.css

144 ms

Our browser made a total of 148 requests to load all elements on the main page. We found that 3% of them (5 requests) were addressed to the original Member.buzz, 97% (143 requests) were made to Resources.member.buzz. The less responsive or slowest element that took the longest time to load (423 ms) belongs to the original domain Member.buzz.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.3 kB (27%)

Content Size

652.4 kB

After Optimization

473.1 kB

In fact, the total size of Member.buzz main page is 652.4 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. 70% of websites need less resources to load. CSS take 245.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 175.7 kB

  • Original 206.8 kB
  • After minification 197.9 kB
  • After compression 31.1 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 175.7 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 3.5 kB

  • Original 180.1 kB
  • After minification 176.6 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. Member images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 5 B

  • Original 19.9 kB
  • After minification 19.9 kB
  • After compression 19.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 158 B

  • Original 245.6 kB
  • After minification 245.6 kB
  • After compression 245.4 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. Member.buzz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 81 (58%)

Requests Now

140

After Optimization

59

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

Accessibility Review

member.buzz accessibility score

71

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

member.buzz best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

member.buzz SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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