Tools & Wizards About Us
build1.io screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% 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

  • 98

    SEO

    Google-friendlier than
    92% of websites

build1.io

Build1 | Game Development Studio

Page Load Speed

542 ms in total

First Response

22 ms

Resources Loaded

351 ms

Page Rendered

169 ms

build1.io screenshot

About Website

Visit build1.io now to see the best up-to-date Build1 content and also check out these interesting facts you probably never knew about build1.io

We deliver Custom Mobile & Web Game Development solutions. Expertise in Unity, backend for games.

Visit build1.io

Key Findings

We analyzed Build1.io page load time and found that the first response time was 22 ms and then it took 520 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

build1.io performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

build1.io

22 ms

build1.io

36 ms

style.css

78 ms

font-awesome.min.css

55 ms

css

54 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 36% of them (12 requests) were addressed to the original Build1.io, 36% (12 requests) were made to Fonts.gstatic.com and 12% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (191 ms) belongs to the original domain Build1.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.3 kB (21%)

Content Size

84.4 kB

After Optimization

67.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Build1.io main page is 84.4 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. 50% of websites need less resources to load. Javascripts take 41.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 8.6 kB

  • Original 11.7 kB
  • After minification 10.5 kB
  • After compression 3.1 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. This page needs HTML code to be minified as it can gain 1.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 8.6 kB or 73% of the original size.

Image Optimization

-23%

Potential reduce by 3.9 kB

  • Original 17.3 kB
  • After minification 13.4 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, Build1 needs image optimization as it can save up to 3.9 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 634 B

  • Original 41.1 kB
  • After minification 40.7 kB
  • After compression 40.5 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

-30%

Potential reduce by 4.2 kB

  • Original 14.2 kB
  • After minification 14.2 kB
  • After compression 10.0 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. Build1.io needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (76%)

Requests Now

17

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

build1.io

build1.io

22 ms

build1.io

build1.io

36 ms

style.css

style.css

78 ms

font-awesome.min.css

font-awesome.min.css

55 ms

css

css

54 ms

css

css

59 ms

push-menu.css

push-menu.css

103 ms

animate.css

animate.css

145 ms

js

js

117 ms

jquery.js

jquery.js

180 ms

jquery-migrate.min.js

jquery-migrate.min.js

99 ms

wow.min.js

wow.min.js

107 ms

wow-init.js

wow-init.js

191 ms

parallax.js

parallax.js

190 ms

font-awesome.min.css

font-awesome.min.css

56 ms

css

css

55 ms

css2

css2

54 ms

logo_big.png

logo_big.png

67 ms

build1.io

build1.io

10 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

26 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

37 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

43 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

54 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf

54 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf

63 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

61 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

62 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

51 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

62 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

63 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf

64 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

21 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

16 ms

Accessibility Review

build1.io accessibility score

96

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

Links do not have a discernible name

Best Practices

build1.io 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

SEO Factors

build1.io SEO score

98

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 Build1.io 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 Build1.io 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

build1.io

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