6.5 sec in total
516 ms
5.3 sec
646 ms
Click here to check amazing WHub content for Hong Kong. Otherwise, check out these important facts you probably never knew about whub.io
Join the Hong Kong's biggest startup community, make meaningful connections with Hong Kong startups, talents and investors. Discover startup events and resources for free.
Visit whub.ioWe analyzed Whub.io page load time and found that the first response time was 516 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whub.io performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.2 s
11/100
25%
Value7.6 s
25/100
10%
Value330 ms
75/100
30%
Value0.044
99/100
15%
Value10.9 s
21/100
10%
516 ms
17 ms
98 ms
38 ms
55 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 26% of them (25 requests) were addressed to the original Whub.io, 19% (18 requests) were made to Sumome-140a.kxcdn.com and 10% (10 requests) were made to Sumome.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source S3-ap-southeast-1.amazonaws.com.
Page size can be reduced by 2.9 MB (36%)
8.0 MB
5.2 MB
In fact, the total size of Whub.io main page is 8.0 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. Only a small number of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 50.2 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 8.7 kB, which is 13% 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 50.2 kB or 76% of the original size.
Potential reduce by 654.6 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, WHub needs image optimization as it can save up to 654.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 923.1 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 923.1 kB or 65% of the original size.
Potential reduce by 1.2 MB
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. Whub.io needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 91% of the original size.
Number of requests can be reduced by 27 (30%)
89
62
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WHub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.whub.io
516 ms
analytics.js
17 ms
mixpanel-2-latest.min.js
98 ms
application-35748a3c0c699c27cb07c80d63a15be9.css
38 ms
css
55 ms
css
54 ms
load.sumome.com
559 ms
jquery.min.js
119 ms
jquery-ui.min.js
133 ms
application-31caf97c9d58d2ffc8e3e867c22df9d2.js
46 ms
raphael-min.js
47 ms
morris.min.js
46 ms
collect
56 ms
sdk.js
77 ms
whub-logo-04-db4c75143d9ae459ce5efddc5e9e2cb7.png
78 ms
Screen_Shot_2016-03-18_at_10.36.19_AM.png
1094 ms
ecommercemarketplace.png
1997 ms
astronaute-kid-a3292987735569804028689bd879c75d.jpg
267 ms
startup-next-0f695798d9ff90769a6d377f9587bf47.png
265 ms
w-hub-logo-white-e585ca5c5af947345453460c73851fc8.png
265 ms
201507-tech-openair-088cc14ee246df36169a7596e47b0ae6.png
269 ms
201506-true-global-venture-a6605b7c9ec6c0966d5f5eeedccec3d2.png
267 ms
201506-google-e2e92ddc5c5015df9c660094ef6ff559.png
266 ms
201505-aisan-entrepreneurs-74a1c19bf3d3213ff0112f2cbaf52353.png
268 ms
2015-06-HKTDC-ce7792ae23ce6516f05ecaf5f1a873ba.jpeg
268 ms
201501-blueprint-42ad15d01df66ed40a2cb5b9a96aace8.png
268 ms
2015-01-Logo-HKUAEC-f749e2bcdb4ed592bd81c305f755716b.png
297 ms
201408-inside-entrepreneurhip-fd035ca9a3f05db4f08c0917799e9c15.png
298 ms
201504-scmp-game-changers-2ea01e0993ded9d0c0a54a01b0d8821b.png
474 ms
201503-youngpost-4f1afdec579e3b694e44537bed39f472.jpeg
299 ms
201407-hket-logo-42967b00cf9e5f01cea5582c7fc50568.jpg
299 ms
2014-07-scmp-33aa7785d105075448ab09c079b363de.jpg
299 ms
2014-Regional-Winner-b531fb1588d548138ba34f9146732ba7.jpg
473 ms
2014-07-EntrepreneurHK-ce583178536d11c6de8003bbf66a99bf.png
471 ms
startuphk-e398237869bbde54f102341e16a28391.jpeg
472 ms
201409-logo-summit-blog-5600364effb17bf081d6c819de1ec2c3.png
472 ms
201409-tvb-pearl-84ff3ee1cc0dea9043dc0cee68a1d478.jpeg
473 ms
morrispropertylogosq.jpg
1336 ms
Honestbee-Logo.png
1279 ms
Social_icon.jpg
1930 ms
gatecoin.png
1076 ms
the-intern-group.png
1087 ms
Blog_Post-1.png
3060 ms
Blog_Post.png
3130 ms
Blog_Post__1_.png
3729 ms
ecommercemarketplace.png
4130 ms
software.png
2211 ms
software.png
3712 ms
hardwareiot.png
2385 ms
hardwareiot.png
3687 ms
all.png
2669 ms
all.png
4419 ms
collect
470 ms
f8OBjBbevvywgbyJOxlO7Q.ttf
271 ms
AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf
273 ms
yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf
273 ms
259 ms
widget_v2.135.js
260 ms
foundation-icons-67cf21e9f64d711a68fd260d7c9a364e.woff
188 ms
324 ms
xd_arbiter.php
50 ms
xd_arbiter.php
68 ms
avatar_simple_visitor.png
52 ms
aL63HcygAAVYuCCsAAA==
1 ms
265 ms
service.js
16 ms
service.js
58 ms
service.js
5 ms
service.js
58 ms
service.js
13 ms
service.js
56 ms
service.js
58 ms
service.js
56 ms
load
222 ms
sumome-scrollbox-popup.css
55 ms
sumome-share-client.css
57 ms
css
21 ms
sme-popup.css
4 ms
sme-contactform-popup.css
13 ms
sumome-smartbar-popup.css
8 ms
load
236 ms
load
291 ms
load
270 ms
load
290 ms
load
262 ms
status
222 ms
status
378 ms
facebook-white-60.png
23 ms
linkedin-white-60.png
8 ms
facebooklike-white-60.png
8 ms
twitter-white-60.png
9 ms
sumome-white-60.png
10 ms
nr-892.min.js
42 ms
collect
38 ms
scroll
98 ms
30ea11f71f
45 ms
whub.io accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
whub.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
whub.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whub.io 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 Whub.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.
whub.io
Open Graph data is detected on the main page of WHub. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: