Tools & Wizards About Us
discussion.community screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

discussion.community

The Easiest Platform To Build Your Own Discussion Community - Website Toolbox

Page Load Speed

195 ms in total

First Response

7 ms

Resources Loaded

188 ms

Page Rendered

0 ms

discussion.community screenshot

About Website

Click here to check amazing Discussion content for United States. Otherwise, check out these important facts you probably never knew about discussion.community

Website Toolbox makes it easily to build an online home for your community. Effortlessly create, grow, and monetize your community with your own community platform. Engage in secure, private, organize...

Visit discussion.community

Key Findings

We analyzed Discussion.community page load time and found that the first response time was 7 ms and then it took 188 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

discussion.community performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,200 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

discussion.community

7 ms

www.websitetoolbox.com

68 ms

j.php

53 ms

js

82 ms

home_min.css

60 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Discussion.community, 40% (6 requests) were made to Cdn.websitetoolbox.com and 20% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (106 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.8 kB (4%)

Content Size

602.7 kB

After Optimization

577.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Discussion.community main page is 602.7 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. 50% of websites need less resources to load. Images take 538.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.4 kB

  • Original 32.7 kB
  • After minification 29.3 kB
  • After compression 8.3 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 24.4 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 300 B

  • Original 538.7 kB
  • After minification 538.4 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. Discussion images are well optimized though.

CSS Optimization

-0%

Potential reduce by 106 B

  • Original 31.3 kB
  • After minification 31.3 kB
  • After compression 31.2 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. Discussion.community has all CSS files already compressed.

Requests Breakdown

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

Requests Now

13

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

discussion.community

discussion.community

7 ms

www.websitetoolbox.com

www.websitetoolbox.com

68 ms

j.php

j.php

53 ms

js

js

82 ms

home_min.css

home_min.css

60 ms

wt_logo_blue.svg

wt_logo_blue.svg

43 ms

css2

css2

54 ms

jquery.min.js

jquery.min.js

56 ms

popper.min.js

popper.min.js

76 ms

bootstrap.min.js

bootstrap.min.js

106 ms

landing_page_min.js

landing_page_min.js

55 ms

loader.js

loader.js

40 ms

theme.svg

theme.svg

5 ms

integration_section.png

integration_section.png

33 ms

quote-logo-4.png

quote-logo-4.png

6 ms

Accessibility Review

discussion.community accessibility score

79

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-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

discussion.community 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

Page has valid source maps

SEO Factors

discussion.community SEO score

100

Search Engine Optimization Advices

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 Discussion.community 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 Discussion.community 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

discussion.community

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