Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

discussions.probrewer.com

Forums - ProBrewer Discussion Board

Page Load Speed

1.1 sec in total

First Response

267 ms

Resources Loaded

560 ms

Page Rendered

248 ms

About Website

Visit discussions.probrewer.com now to see the best up-to-date Discussion S Pro Brewer content for United States and also check out these interesting facts you probably never knew about discussions.probrewer.com

vBulletin Forums

Visit discussions.probrewer.com

Key Findings

We analyzed Discussions.probrewer.com page load time and found that the first response time was 267 ms and then it took 808 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

discussions.probrewer.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

74/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

discussions.probrewer.com

267 ms

yuiloader-dom-event.js

63 ms

connection-min.js

34 ms

vbulletin-core.js

77 ms

css.php

164 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 81% of them (25 requests) were addressed to the original Discussions.probrewer.com, 6% (2 requests) were made to Stats.g.doubleclick.net and 3% (1 request) were made to Googletagservices.com. The less responsive or slowest element that took the longest time to load (267 ms) belongs to the original domain Discussions.probrewer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.7 kB (69%)

Content Size

464.6 kB

After Optimization

145.9 kB

In fact, the total size of Discussions.probrewer.com main page is 464.6 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. Javascripts take 309.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.6 kB

  • Original 44.0 kB
  • After minification 40.5 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 35.6 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 1.1 kB

  • Original 12.1 kB
  • After minification 11.0 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 S Pro Brewer images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 196.6 kB

  • Original 309.2 kB
  • After minification 307.9 kB
  • After compression 112.6 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 196.6 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 85.5 kB

  • Original 99.4 kB
  • After minification 77.4 kB
  • After compression 13.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. Discussions.probrewer.com needs all CSS files to be minified and compressed as it can save up to 85.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

8

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

Accessibility Review

discussions.probrewer.com 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.

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

<frame> or <iframe> elements do not have a title

Best Practices

discussions.probrewer.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

discussions.probrewer.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discussions.probrewer.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 Discussions.probrewer.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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