Tools & Wizards About Us
big.community screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

big.community

Big Community

Page Load Speed

5.2 sec in total

First Response

27 ms

Resources Loaded

5.1 sec

Page Rendered

51 ms

big.community screenshot

About Website

Welcome to big.community homepage info - get ready to check Big best content for Canada right away, or after learning these important things about big.community

Funny Posts and Memes

Visit big.community

Key Findings

We analyzed Big.community page load time and found that the first response time was 27 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

big.community performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

big.community

27 ms

big.community

4794 ms

color_definitions_light_2_3_5f13a49a8e4fb0a0617ae8537d901bcf27af47ae.css

18 ms

desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

47 ms

chat_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

27 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 96% of them (24 requests) were addressed to the original Big.community, 4% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Big.community.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.9 kB (35%)

Content Size

558.2 kB

After Optimization

360.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Big.community main page is 558.2 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. 20% of websites need less resources to load. HTML takes 225.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 197.6 kB

  • Original 225.4 kB
  • After minification 213.0 kB
  • After compression 27.8 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 197.6 kB or 88% of the original size.

JavaScript Optimization

-0%

Potential reduce by 28 B

  • Original 195.3 kB
  • After minification 195.3 kB
  • After compression 195.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.

CSS Optimization

-0%

Potential reduce by 267 B

  • Original 137.6 kB
  • After minification 137.6 kB
  • After compression 137.3 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. Big.community has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (91%)

Requests Now

23

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Big. 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 JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

big.community

big.community

27 ms

big.community

big.community

4794 ms

color_definitions_light_2_3_5f13a49a8e4fb0a0617ae8537d901bcf27af47ae.css

color_definitions_light_2_3_5f13a49a8e4fb0a0617ae8537d901bcf27af47ae.css

18 ms

desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

47 ms

chat_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

chat_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

27 ms

checklist_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

checklist_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

31 ms

discourse-adplugin_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-adplugin_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

32 ms

discourse-details_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-details_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

32 ms

discourse-lazy-videos_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-lazy-videos_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

32 ms

discourse-local-dates_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-local-dates_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

39 ms

discourse-narrative-bot_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-narrative-bot_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

69 ms

discourse-presence_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-presence_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

40 ms

discourse-reactions_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-reactions_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

40 ms

discourse-solved_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-solved_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

43 ms

docker_manager_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

docker_manager_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

67 ms

footnote_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

footnote_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

67 ms

poll_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

poll_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

65 ms

spoiler-alert_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

spoiler-alert_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

71 ms

chat_desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

chat_desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

67 ms

discourse-reactions_desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

discourse-reactions_desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

67 ms

poll_desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

poll_desktop_20eb3736d5781f7fdbaf1463284baa8b54f73356.css

68 ms

rocket-loader.min.js

rocket-loader.min.js

64 ms

adsbygoogle.js

adsbygoogle.js

128 ms

browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.js

browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.js

78 ms

vendor.ff29780b9fed784cce2d843dcb93a803-608f4f77d8437d715d8d39c739c0c8bbe0fe51c9305e55f1ec7d0bee19f5571f.js

vendor.ff29780b9fed784cce2d843dcb93a803-608f4f77d8437d715d8d39c739c0c8bbe0fe51c9305e55f1ec7d0bee19f5571f.js

85 ms

Accessibility Review

big.community accessibility score

97

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

big.community best practices score

83

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

Page has valid source maps

SEO Factors

big.community SEO score

95

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

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 Big.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 Big.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

big.community

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