Tools & Wizards About Us
support.cmnty.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

support.cmnty.com

Getting Started Archives - CMNTY Help Center

Page Load Speed

2.5 sec in total

First Response

153 ms

Resources Loaded

2.2 sec

Page Rendered

114 ms

support.cmnty.com screenshot

About Website

Click here to check amazing Support CMNTY content for United States. Otherwise, check out these important facts you probably never knew about support.cmnty.com

Getting Started Archives

Visit support.cmnty.com

Key Findings

We analyzed Support.cmnty.com page load time and found that the first response time was 153 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

support.cmnty.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

support.cmnty.com

153 ms

support.cmnty.com

286 ms

413 ms

417 ms

482 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Support.cmnty.com, 40% (10 requests) were made to Support.marketresponsegroup.com and 32% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (482 ms) relates to the external source Support.marketresponsegroup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.3 kB (10%)

Content Size

204.7 kB

After Optimization

183.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Support.cmnty.com main page is 204.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. 30% of websites need less resources to load. CSS take 113.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.4 kB

  • Original 23.4 kB
  • After minification 23.4 kB
  • After compression 6.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 17.4 kB or 74% of the original size.

Image Optimization

-31%

Potential reduce by 3.7 kB

  • Original 12.0 kB
  • After minification 8.3 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. Obviously, Support CMNTY needs image optimization as it can save up to 3.7 kB or 31% 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 24 B

  • Original 55.8 kB
  • After minification 55.8 kB
  • After compression 55.8 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 273 B

  • Original 113.5 kB
  • After minification 113.5 kB
  • After compression 113.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. Support.cmnty.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (30%)

Requests Now

10

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

support.cmnty.com

support.cmnty.com

153 ms

support.cmnty.com

support.cmnty.com

286 ms

413 ms

417 ms

482 ms

gtm.js

gtm.js

75 ms

autoptimize_05fb600ef22e14d2a34f2355e5a6745a.css

autoptimize_05fb600ef22e14d2a34f2355e5a6745a.css

142 ms

autoptimize_00df71b5809d374b00ce03791ac8fac1.css

autoptimize_00df71b5809d374b00ce03791ac8fac1.css

218 ms

css

css

32 ms

css

css

48 ms

autoptimize_single_49edccea2e7ba985cadc9ba0531cbed1.js

autoptimize_single_49edccea2e7ba985cadc9ba0531cbed1.js

285 ms

autoptimize_ae03bb2be62abc9a5da8b4ad20e8b2ff.js

autoptimize_ae03bb2be62abc9a5da8b4ad20e8b2ff.js

333 ms

blue-header-background.png

blue-header-background.png

80 ms

MR-CMNTY-logo_wit_RGB_500x146px.png

MR-CMNTY-logo_wit_RGB_500x146px.png

76 ms

mask.svg

mask.svg

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

14 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

18 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

20 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iQ.woff

29 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

145 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

151 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

11 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

10 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

10 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

21 ms

Accessibility Review

support.cmnty.com 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

Image elements do not have [alt] attributes

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

support.cmnty.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

support.cmnty.com SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Support.cmnty.com 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 Support.cmnty.com 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

support.cmnty.com

Open Graph data is detected on the main page of Support CMNTY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: