Tools & Wizards About Us
community.frame.work screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

community.frame.work

Framework Community - Discussion and support for Framework products

Page Load Speed

635 ms in total

First Response

55 ms

Resources Loaded

493 ms

Page Rendered

87 ms

community.frame.work screenshot

About Website

Visit community.frame.work now to see the best up-to-date Community Frame content for United States and also check out these interesting facts you probably never knew about community.frame.work

The Framework Community: an online forum where you can connect with us and each other for discussions and support around the mission and products

Visit community.frame.work

Key Findings

We analyzed Community.frame.work page load time and found that the first response time was 55 ms and then it took 580 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

community.frame.work performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

community.frame.work

55 ms

community.frame.work

246 ms

browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.js

26 ms

vendor.f196a698a6a811ae0583c1ea5284644b-53642a3b547b78e34800ab2eeb101f12b39be8c27ec85e9ad359a095161fad6b.js

52 ms

chunk.7146f8cf70b2fc83db43.d41d8cd9.js

200 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that all of those requests were addressed to Community.frame.work and no external sources were called. The less responsive or slowest element that took the longest time to load (246 ms) belongs to the original domain Community.frame.work.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.2 kB (13%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Community.frame.work main page is 1.6 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. 25% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 168.3 kB

  • Original 203.0 kB
  • After minification 198.2 kB
  • After compression 34.6 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 168.3 kB or 83% of the original size.

JavaScript Optimization

-0%

Potential reduce by 454 B

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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

-23%

Potential reduce by 33.5 kB

  • Original 144.0 kB
  • After minification 112.1 kB
  • After compression 110.6 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. Community.frame.work needs all CSS files to be minified and compressed as it can save up to 33.5 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (94%)

Requests Now

36

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

community.frame.work

community.frame.work

55 ms

community.frame.work

community.frame.work

246 ms

browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.js

browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.js

26 ms

vendor.f196a698a6a811ae0583c1ea5284644b-53642a3b547b78e34800ab2eeb101f12b39be8c27ec85e9ad359a095161fad6b.js

vendor.f196a698a6a811ae0583c1ea5284644b-53642a3b547b78e34800ab2eeb101f12b39be8c27ec85e9ad359a095161fad6b.js

52 ms

chunk.7146f8cf70b2fc83db43.d41d8cd9.js

chunk.7146f8cf70b2fc83db43.d41d8cd9.js

200 ms

chunk.424a5e7ed08fc6f8b007.d41d8cd9.js

chunk.424a5e7ed08fc6f8b007.d41d8cd9.js

32 ms

checklist-273fb3ab5f7d346fa16c1482aedbd81035c5f677a83d7940da78abf7c1e16744.js

checklist-273fb3ab5f7d346fa16c1482aedbd81035c5f677a83d7940da78abf7c1e16744.js

29 ms

discourse-details-48148ec534a4c5e9614302186b345123ba1358787c41bc31cbd17231f794fe42.js

discourse-details-48148ec534a4c5e9614302186b345123ba1358787c41bc31cbd17231f794fe42.js

39 ms

discourse-lazy-videos-63eed75cfc7d9d359404a745e831548ec1fee6c0f13a5be7a8a69adf71bfefb4.js

discourse-lazy-videos-63eed75cfc7d9d359404a745e831548ec1fee6c0f13a5be7a8a69adf71bfefb4.js

41 ms

discourse-local-dates-a1b9590bc8f26e3bcd3d4cf00594250816149a8c4f00c75ffed0bfcf3e409d74.js

discourse-local-dates-a1b9590bc8f26e3bcd3d4cf00594250816149a8c4f00c75ffed0bfcf3e409d74.js

44 ms

discourse-narrative-bot-643f10339e287d380f81413fde738a8ad3a6e2a5ee4d7e30f2e841f92c78e5eb.js

discourse-narrative-bot-643f10339e287d380f81413fde738a8ad3a6e2a5ee4d7e30f2e841f92c78e5eb.js

53 ms

discourse-presence-fc08c21eda4e026fe0e91d04f30a77cd839e6e0c9e443bc9bd9817cb6eddf0d4.js

discourse-presence-fc08c21eda4e026fe0e91d04f30a77cd839e6e0c9e443bc9bd9817cb6eddf0d4.js

73 ms

footnote-9e6a21e04868e13dc75adf73cfaab1be722d32b46af9a8b1894712c647ab6499.js

footnote-9e6a21e04868e13dc75adf73cfaab1be722d32b46af9a8b1894712c647ab6499.js

65 ms

footnote_extra-7f7bb8e0891106317fe6883ba187d239709a385df2c386a4d9ab105732204444.js

footnote_extra-7f7bb8e0891106317fe6883ba187d239709a385df2c386a4d9ab105732204444.js

82 ms

framework-segment-f2c159184af0a7603b9893664b64953da969cdf47f3a872d322aaa45e86a548f.js

framework-segment-f2c159184af0a7603b9893664b64953da969cdf47f3a872d322aaa45e86a548f.js

70 ms

framework-sentry-90d232544cd7b618c5bd951b7e47d0f1ed2e4bbe767f2777b063df4b9190598e.js

framework-sentry-90d232544cd7b618c5bd951b7e47d0f1ed2e4bbe767f2777b063df4b9190598e.js

80 ms

poll-c514fbef324ad213e9825daf68ecdfebd34a708e617429299d36fa1dd3fd6c6f.js

poll-c514fbef324ad213e9825daf68ecdfebd34a708e617429299d36fa1dd3fd6c6f.js

98 ms

spoiler-alert-77512c36f465902e7dbf3b8252c7cd6387edc9bf4ca804b79466212c1d1c843d.js

spoiler-alert-77512c36f465902e7dbf3b8252c7cd6387edc9bf4ca804b79466212c1d1c843d.js

84 ms

en-02dd3e2ae27a2d690ba187cc03dde7537da4eda09ffe5daf46e6beecdc9e9c1c.js

en-02dd3e2ae27a2d690ba187cc03dde7537da4eda09ffe5daf46e6beecdc9e9c1c.js

98 ms

18629fe63f47e364de7a49357170e379af880b3d.js

18629fe63f47e364de7a49357170e379af880b3d.js

103 ms

206ea8c2339d0357603a61f8f9c3838d0d890b57.js

206ea8c2339d0357603a61f8f9c3838d0d890b57.js

98 ms

color_definitions_framework_45_48_4f631d039dc91706ab47a609e7389d84c13b842a.css

color_definitions_framework_45_48_4f631d039dc91706ab47a609e7389d84c13b842a.css

97 ms

desktop_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

desktop_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

121 ms

checklist_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

checklist_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

108 ms

discourse-details_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

discourse-details_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

112 ms

discourse-lazy-videos_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

discourse-lazy-videos_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

117 ms

discourse-local-dates_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

discourse-local-dates_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

117 ms

discourse-narrative-bot_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

discourse-narrative-bot_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

156 ms

discourse-presence_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

discourse-presence_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

158 ms

footnote_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

footnote_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

160 ms

poll_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

poll_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

160 ms

spoiler-alert_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

spoiler-alert_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

157 ms

poll_desktop_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

poll_desktop_ea345f1d1e1cd1974ef1c856be0af65bb7a15a6e.css

159 ms

desktop_theme_13_71174b82b569b5991c7c942a52042160e9135856.css

desktop_theme_13_71174b82b569b5991c7c942a52042160e9135856.css

176 ms

desktop_theme_49_9520b7fac07d17ae7722e8011665d13c09b31598.css

desktop_theme_49_9520b7fac07d17ae7722e8011665d13c09b31598.css

176 ms

desktop_theme_48_06458b17730f8576f2b5213eb3cb15cdc562d16e.css

desktop_theme_48_06458b17730f8576f2b5213eb3cb15cdc562d16e.css

176 ms

start-discourse-7c0f5f4daf3c942b7b6ecfe8e62e2e5a0f6555924859cf055314c0df3d617353.js

start-discourse-7c0f5f4daf3c942b7b6ecfe8e62e2e5a0f6555924859cf055314c0df3d617353.js

116 ms

browser-update-9070f07226d022f68c06506e046ae33f8fe725302ff53955cd3d483f2fc47ff6.js

browser-update-9070f07226d022f68c06506e046ae33f8fe725302ff53955cd3d483f2fc47ff6.js

114 ms

Accessibility Review

community.frame.work accessibility score

96

Accessibility Issues

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

community.frame.work best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

community.frame.work 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 Community.frame.work 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 Community.frame.work 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.frame.work

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