Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

hub.com

HUB: Connect on One Platform

Page Load Speed

1.1 sec in total

First Response

261 ms

Resources Loaded

664 ms

Page Rendered

125 ms

hub.com screenshot

About Website

Visit hub.com now to see the best up-to-date HUB content for United States and also check out these interesting facts you probably never knew about hub.com

Build seamless connectivity between data and trading to optimise your investment operations' technology

Visit hub.com

Key Findings

We analyzed Hub.com page load time and found that the first response time was 261 ms and then it took 789 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

hub.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

www.hub.com

261 ms

23 ms

MarkitCore.css

34 ms

Common.css

66 ms

entrypoint.css

50 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 95% of them (18 requests) were addressed to the original Hub.com, 5% (1 request) were made to Ad.wsod.com. The less responsive or slowest element that took the longest time to load (261 ms) belongs to the original domain Hub.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.4 kB (61%)

Content Size

506.8 kB

After Optimization

198.4 kB

In fact, the total size of Hub.com main page is 506.8 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. Only 10% of websites need less resources to load. CSS take 217.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 14.7 kB

  • Original 18.7 kB
  • After minification 15.5 kB
  • After compression 3.9 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 3.2 kB, which is 17% 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 14.7 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 32.3 kB

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

JavaScript Optimization

-65%

Potential reduce by 76.1 kB

  • Original 117.9 kB
  • After minification 117.3 kB
  • After compression 41.8 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 76.1 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 185.3 kB

  • Original 217.8 kB
  • After minification 164.1 kB
  • After compression 32.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. Hub.com needs all CSS files to be minified and compressed as it can save up to 185.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (44%)

Requests Now

16

After Optimization

9

The browser has sent 16 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 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

hub.com accessibility score

78

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

Form elements do not have associated labels

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

hub.com 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

hub.com SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hub.com 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 Hub.com 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

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