Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 100

    SEO

    Google-friendlier than
    96% of websites

discussion.community

The Intuitive Platform To Create Your Own Forum - Website Toolbox

Page Load Speed

816 ms in total

First Response

39 ms

Resources Loaded

555 ms

Page Rendered

222 ms

discussion.community screenshot

About Website

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

Effortlessly engage your audience under your brand with a stand-alone or integrated community. We make creating a forum simple, easy, and user-friendly.

Visit discussion.community

Key Findings

We analyzed Discussion.community page load time and found that the first response time was 39 ms and then it took 777 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

discussion.community performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

discussion.community

39 ms

index.html

63 ms

layout.css

11 ms

signup.css

19 ms

jquery-ui.css

54 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Discussion.community, 59% (16 requests) were made to Websitetoolbox.com and 11% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (145 ms) relates to the external source Ajax.googleapis.com.

Page Optimization Overview & Recommendations

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

Content Size

434.1 kB

After Optimization

318.4 kB

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

HTML Optimization

-70%

Potential reduce by 11.4 kB

  • Original 16.3 kB
  • After minification 13.3 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 18% 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 11.4 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 4.3 kB

  • Original 246.5 kB
  • After minification 242.2 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.

JavaScript Optimization

-36%

Potential reduce by 30.3 kB

  • Original 83.7 kB
  • After minification 83.7 kB
  • After compression 53.5 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 30.3 kB or 36% of the original size.

CSS Optimization

-80%

Potential reduce by 69.7 kB

  • Original 87.6 kB
  • After minification 85.4 kB
  • After compression 17.9 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 needs all CSS files to be minified and compressed as it can save up to 69.7 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

17

The browser has sent 23 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.

Accessibility Review

discussion.community accessibility score

81

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.

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

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: