Tools & Wizards About Us
hub.org screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

hub.org

Page Load Speed

3.6 sec in total

First Response

203 ms

Resources Loaded

2.6 sec

Page Rendered

779 ms

hub.org screenshot

About Website

Visit hub.org now to see the best up-to-date Hub content for Canada and also check out these interesting facts you probably never knew about hub.org

Turn-key hosting and reliable computer system solutions for startups and SME owners

Visit hub.org

Key Findings

We analyzed Hub.org page load time and found that the first response time was 203 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hub.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

hub.org

203 ms

www.hub.org

1477 ms

style.css

547 ms

twitter-feed.css

158 ms

dashicons.min.css

237 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 62% of them (16 requests) were addressed to the original Hub.org, 15% (4 requests) were made to and 12% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Hub.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 734.9 kB (28%)

Content Size

2.7 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hub.org main page is 2.7 MB. 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 370.5 kB

  • Original 620.6 kB
  • After minification 616.7 kB
  • After compression 250.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. 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 370.5 kB or 60% of the original size.

Image Optimization

-6%

Potential reduce by 91.5 kB

  • Original 1.4 MB
  • After minification 1.4 MB

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. Hub images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 173.0 kB

  • Original 258.3 kB
  • After minification 249.5 kB
  • After compression 85.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 173.0 kB or 67% of the original size.

CSS Optimization

-30%

Potential reduce by 99.9 kB

  • Original 338.1 kB
  • After minification 333.8 kB
  • After compression 238.2 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. Hub.org needs all CSS files to be minified and compressed as it can save up to 99.9 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (60%)

Requests Now

20

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hub.org

hub.org

203 ms

www.hub.org

www.hub.org

1477 ms

style.css

style.css

547 ms

twitter-feed.css

twitter-feed.css

158 ms

dashicons.min.css

dashicons.min.css

237 ms

thickbox.css

thickbox.css

172 ms

jquery.js

jquery.js

239 ms

jquery-migrate.min.js

jquery-migrate.min.js

235 ms

gk-nsp.js

gk-nsp.js

81 ms

thickbox.js

thickbox.js

81 ms

wp-embed.min.js

wp-embed.min.js

83 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

191 ms

analytics.js

analytics.js

182 ms

primary-header-background.jpg

primary-header-background.jpg

651 ms

secondary-header-background.jpg

secondary-header-background.jpg

269 ms

frescochat.js

frescochat.js

274 ms

UNMAAAFUvTYbAAA=

UNMAAAFUvTYbAAA=

29 ms

avse5+kKwZl0sOLty3og715wT7o+3+m5Kk3G55dUgAAAVS9OY4AAA==

avse5+kKwZl0sOLty3og715wT7o+3+m5Kk3G55dUgAAAVS9OY4AAA==

28 ms

ucaxh1Q5L2JWAZWOJuhKy+Vhi3IruAxNk3A5MkcljYIZMi54KcvkF9opQDQAAAAFUvTelAAA=

ucaxh1Q5L2JWAZWOJuhKy+Vhi3IruAxNk3A5MkcljYIZMi54KcvkF9opQDQAAAAFUvTelAAA=

27 ms

2uhC7Gg2527Zn7Cb72hZtSbFsKN8hnOWEbLFvDeJFRVxsyC6qO3+a4gsLsDuFAWCtFJzPjBRcwDkpDAF3+QMjT936aL2xKXpeH8EA9KeaIRh0miMwXGtG4EhoxmA010zAeKaZgslBMwPTUjMHs8WfknLxBiinU10AAVS9OeoAAA==

2uhC7Gg2527Zn7Cb72hZtSbFsKN8hnOWEbLFvDeJFRVxsyC6qO3+a4gsLsDuFAWCtFJzPjBRcwDkpDAF3+QMjT936aL2xKXpeH8EA9KeaIRh0miMwXGtG4EhoxmA010zAeKaZgslBMwPTUjMHs8WfknLxBiinU10AAVS9OeoAAA==

26 ms

linkid.js

linkid.js

18 ms

loadingAnimation.gif

loadingAnimation.gif

85 ms

menu-border.png

menu-border.png

84 ms

collect

collect

99 ms

collect

collect

97 ms

9c3be6b4-e3ec-48cb-b871-f794f76ade65.js

9c3be6b4-e3ec-48cb-b871-f794f76ade65.js

336 ms

Accessibility Review

hub.org accessibility score

68

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

Document doesn't have a <title> element

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

hub.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

hub.org SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hub.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Hub.org 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

hub.org

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