Tools & Wizards About Us
builds.gg screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

builds.gg

builds.gg

Page Load Speed

3 sec in total

First Response

210 ms

Resources Loaded

2 sec

Page Rendered

792 ms

builds.gg screenshot

About Website

Welcome to builds.gg homepage info - get ready to check Builds best content for United States right away, or after learning these important things about builds.gg

builds.gg is an online community for PC builders from across the globe. Created by some of the world's most prolific PC builders, builds.gg connects people with a common passion for everything PC and ...

Visit builds.gg

Key Findings

We analyzed Builds.gg page load time and found that the first response time was 210 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

builds.gg performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value2,250 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.316

37/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

builds.gg

210 ms

builds.gg

467 ms

libraries-73bfd83570.css

436 ms

app-63ff700892.css

361 ms

OneSignalSDK.js

73 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Builds.gg, 72% (26 requests) were made to A1.builds.gg and 11% (4 requests) were made to P1.builds.gg. The less responsive or slowest element that took the longest time to load (766 ms) relates to the external source A1.builds.gg.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.6 kB (9%)

Content Size

621.0 kB

After Optimization

567.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Builds.gg main page is 621.0 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. 40% of websites need less resources to load. Images take 311.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 40.2 kB

  • Original 52.2 kB
  • After minification 49.7 kB
  • After compression 12.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 40.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 370 B

  • Original 311.1 kB
  • After minification 310.7 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. Builds images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 223 B

  • Original 226.7 kB
  • After minification 226.7 kB
  • After compression 226.4 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

-41%

Potential reduce by 12.8 kB

  • Original 31.0 kB
  • After minification 18.3 kB
  • After compression 18.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. Builds.gg needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (31%)

Requests Now

29

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

builds.gg

builds.gg

210 ms

builds.gg

builds.gg

467 ms

libraries-73bfd83570.css

libraries-73bfd83570.css

436 ms

app-63ff700892.css

app-63ff700892.css

361 ms

OneSignalSDK.js

OneSignalSDK.js

73 ms

libraries-8e9066135a.js

libraries-8e9066135a.js

55 ms

components-568d487391.js

components-568d487391.js

96 ms

select2-0f64f3a3a0.js

select2-0f64f3a3a0.js

49 ms

swiper-24fd8f7966.js

swiper-24fd8f7966.js

56 ms

app-b10e0cf8d0.js

app-b10e0cf8d0.js

102 ms

login_signup-d4a7452885.js

login_signup-d4a7452885.js

58 ms

feed-e4a4e2ac9e.js

feed-e4a4e2ac9e.js

61 ms

script.js

script.js

44 ms

piwik.js

piwik.js

573 ms

start_three.png

start_three.png

23 ms

howto_1.jpg

howto_1.jpg

23 ms

howto_2.jpg

howto_2.jpg

21 ms

howto_3.jpg

howto_3.jpg

23 ms

howto_4.jpg

howto_4.jpg

21 ms

builds_bronze.svg

builds_bronze.svg

160 ms

views_bronze.svg

views_bronze.svg

125 ms

builds_red2.svg

builds_red2.svg

233 ms

views_gold.svg

views_gold.svg

197 ms

trekade_logo_white_horizontal.svg

trekade_logo_white_horizontal.svg

304 ms

85467_1612716374.jpg

85467_1612716374.jpg

136 ms

top_start.jpg

top_start.jpg

69 ms

user_picture_default.jpg

user_picture_default.jpg

68 ms

89309_1616251517.jpg

89309_1616251517.jpg

112 ms

244_1546731795.jpg

244_1546731795.jpg

117 ms

83361_1711894457.jpg

83361_1711894457.jpg

113 ms

fa-regular-400.ttf

fa-regular-400.ttf

15 ms

fa-light-300.ttf

fa-light-300.ttf

691 ms

fa-thin-100.ttf

fa-thin-100.ttf

766 ms

fa-solid-900.ttf

fa-solid-900.ttf

718 ms

fa-duotone-900.ttf

fa-duotone-900.ttf

83 ms

piwik.php

piwik.php

168 ms

Accessibility Review

builds.gg 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

builds.gg 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

builds.gg SEO score

89

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

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 Builds.gg 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 Builds.gg 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

builds.gg

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