Tools & Wizards About Us
hubble.build screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

hubble.build

Construction Management Software - Digital Platform Solution

Page Load Speed

1.1 sec in total

First Response

525 ms

Resources Loaded

536 ms

Page Rendered

58 ms

hubble.build screenshot

About Website

Visit hubble.build now to see the best up-to-date Hubble content and also check out these interesting facts you probably never knew about hubble.build

Build better, faster, safer & cost-effective with digital construction platform management software. Learn how to digitise & automate worksite workflows.

Visit hubble.build

Key Findings

We analyzed Hubble.build page load time and found that the first response time was 525 ms and then it took 594 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

hubble.build performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value27.5 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,050 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

hubble.build

525 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 133.1 kB (16%)

Content Size

845.6 kB

After Optimization

712.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hubble.build main page is 845.6 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 614.4 kB which makes up the majority of the site volume.

HTML Optimization

-35%

Potential reduce by 54 B

  • Original 156 B
  • After minification 154 B
  • After compression 102 B

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 54 B or 35% of the original size.

Image Optimization

-20%

Potential reduce by 124.0 kB

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

JavaScript Optimization

-5%

Potential reduce by 4.1 kB

  • Original 84.6 kB
  • After minification 84.5 kB
  • After compression 80.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

-3%

Potential reduce by 5.0 kB

  • Original 146.4 kB
  • After minification 146.4 kB
  • After compression 141.5 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. Hubble.build has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Network Requests Diagram

hubble.build

hubble.build

525 ms

Accessibility Review

hubble.build accessibility score

75

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

hubble.build 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hubble.build 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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hubble.build can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hubble.build main page’s claimed encoding is . 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

hubble.build

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