Tools & Wizards About Us
community.beam.gg screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

community.beam.gg

Beam.gg Community - | Gamifying the Online Community Experience

Page Load Speed

1.4 sec in total

First Response

9 ms

Resources Loaded

1.3 sec

Page Rendered

108 ms

community.beam.gg screenshot

About Website

Click here to check amazing Community Beam content for United States. Otherwise, check out these important facts you probably never knew about community.beam.gg

Start a community or grow an existing one with the all-in-one community platform. Try Beam.gg for free and get more than just discussion forums.

Visit community.beam.gg

Key Findings

We analyzed Community.beam.gg page load time and found that the first response time was 9 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

community.beam.gg performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value2,820 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value31.1 s

0/100

10%

Network Requests Diagram

community.beam.gg

9 ms

community.beam.gg

748 ms

js

73 ms

js

67 ms

0202f9d342762cfa.css

15 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 46% of them (23 requests) were addressed to the original Community.beam.gg, 30% (15 requests) were made to Community-platform-bucket-prod.s3.amazonaws.com and 14% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (748 ms) belongs to the original domain Community.beam.gg.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (39%)

Content Size

4.5 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Community.beam.gg main page is 4.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. 65% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 204.3 kB

  • Original 238.3 kB
  • After minification 238.1 kB
  • After compression 34.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 204.3 kB or 86% of the original size.

Image Optimization

-37%

Potential reduce by 1.6 MB

  • Original 4.2 MB
  • After minification 2.6 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. Obviously, Community Beam needs image optimization as it can save up to 1.6 MB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 19 (46%)

Requests Now

41

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

community.beam.gg

community.beam.gg

9 ms

community.beam.gg

community.beam.gg

748 ms

js

js

73 ms

js

js

67 ms

0202f9d342762cfa.css

0202f9d342762cfa.css

15 ms

0ecff18c740e86ff.css

0ecff18c740e86ff.css

42 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

30 ms

webpack-deae708b25573698.js

webpack-deae708b25573698.js

26 ms

framework-ce84985cd166733a.js

framework-ce84985cd166733a.js

55 ms

main-e056737ceb956853.js

main-e056737ceb956853.js

38 ms

_app-a8e98356a4ea2fb8.js

_app-a8e98356a4ea2fb8.js

224 ms

3c7ab785-e4a3a150e2af1bad.js

3c7ab785-e4a3a150e2af1bad.js

50 ms

75fc9c18-77eb3eed1ce8b154.js

75fc9c18-77eb3eed1ce8b154.js

199 ms

ef0e3b0f-49d9baeed3569f33.js

ef0e3b0f-49d9baeed3569f33.js

58 ms

48d448c8-a4959d4cd52c9a85.js

48d448c8-a4959d4cd52c9a85.js

65 ms

bee240a3-41a0eefec2ab12ef.js

bee240a3-41a0eefec2ab12ef.js

199 ms

fc83e031-dac08ccaa099c7b7.js

fc83e031-dac08ccaa099c7b7.js

203 ms

8571-9629774308772791.js

8571-9629774308772791.js

276 ms

3259-24b1dad6dc8cbdab.js

3259-24b1dad6dc8cbdab.js

243 ms

3-02e6ef1235e392a0.js

3-02e6ef1235e392a0.js

199 ms

7641-8abc98fff3c87c4a.js

7641-8abc98fff3c87c4a.js

243 ms

index-421413d836fe9ce2.js

index-421413d836fe9ce2.js

200 ms

_buildManifest.js

_buildManifest.js

237 ms

_ssgManifest.js

_ssgManifest.js

237 ms

communityIcon.png

communityIcon.png

222 ms

Summer.png

Summer.png

251 ms

Gold_Animated.png

Gold_Animated.png

222 ms

Pink_Blue.png

Pink_Blue.png

212 ms

communityBanner.png

communityBanner.png

231 ms

profilePicture.jpeg

profilePicture.jpeg

183 ms

banner_wa48krgoyw7i.png

banner_wa48krgoyw7i.png

225 ms

profilePicture.jpeg

profilePicture.jpeg

212 ms

49rwxh38kixwawfw.jpg

49rwxh38kixwawfw.jpg

264 ms

profilePicture.jpeg

profilePicture.jpeg

212 ms

profilePicture.jpeg

profilePicture.jpeg

214 ms

profilePicture.png

profilePicture.png

237 ms

avatar_3e3cs8lpfwyxmz.jpeg

avatar_3e3cs8lpfwyxmz.jpeg

239 ms

avatar_p4nme8leay45yn.jpeg

avatar_p4nme8leay45yn.jpeg

260 ms

banner_218_31up07m8leaz1s5h.png

banner_218_31up07m8leaz1s5h.png

317 ms

profilePicture.jpeg

profilePicture.jpeg

258 ms

banner_217_452348leaz0n0e.png

banner_217_452348leaz0n0e.png

316 ms

banner_216_452348leayxxgu.png

banner_216_452348leayxxgu.png

322 ms

default-frame.svg

default-frame.svg

126 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

23 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

45 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

58 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

58 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

60 ms

Accessibility Review

community.beam.gg accessibility score

75

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

Buttons do not have an accessible name

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.

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

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.

Best Practices

community.beam.gg 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

Missing source maps for large first-party JavaScript

SEO Factors

community.beam.gg SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.beam.gg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Community.beam.gg 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

community.beam.gg

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