7.5 sec in total
443 ms
6.3 sec
744 ms
Visit hub.id now to see the best up-to-date Hub content for Indonesia and also check out these interesting facts you probably never knew about hub.id
Visit hub.idWe analyzed Hub.id page load time and found that the first response time was 443 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hub.id performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value20.6 s
0/100
25%
Value12.1 s
4/100
10%
Value410 ms
67/100
30%
Value0
100/100
15%
Value21.6 s
1/100
10%
443 ms
1360 ms
83 ms
39 ms
688 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 30% of them (27 requests) were addressed to the original Hub.id, 55% (49 requests) were made to S3.hub.id and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source S3.hub.id.
Page size can be reduced by 12.0 MB (59%)
20.5 MB
8.5 MB
In fact, the total size of Hub.id main page is 20.5 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. 65% of websites need less resources to load. Images take 19.7 MB which makes up the majority of the site volume.
Potential reduce by 94.7 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 30.0 kB, which is 27% 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 94.7 kB or 86% of the original size.
Potential reduce by 11.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. Obviously, Hub needs image optimization as it can save up to 11.4 MB or 58% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 525.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.id needs all CSS files to be minified and compressed as it can save up to 525.2 kB or 84% of the original size.
Number of requests can be reduced by 15 (19%)
78
63
The browser has sent 78 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 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hub.id
443 ms
hub.id
1360 ms
js
83 ms
daterangepicker.css
39 ms
app-c49eac01.css
688 ms
fontawesome-2409ab5a.css
1954 ms
swiper-997cc8e5.css
663 ms
pagination-1f52dca1.css
667 ms
navigation-b681b4e7.css
693 ms
oZiBdsevGxiAV8SLPYAHq72LWc5l032ZvL1e3nsX.png
2231 ms
1XRaeQe2vNzj5acmUyhdGsPl1erwKNqK2vRdrYIQ.jpg
2145 ms
Kw3a4SFcV3Ob7BAQpsWfbEoK4WlZFVEzH69WrYvh.jpg
2729 ms
4L1e2SNqaxg358YgAi3pPuiODlSFZjZ3vHxRVCD7.jpg
1603 ms
1PlZr47lSxdoJduW0V1R0zLA2xZRuktHhACBOu3Y.png
2492 ms
dFJHbnVWBbT4lTcvrwDrT4jLKUP8t5RUuVIfaNRj.svg
955 ms
4brcpDL7ETss70C7otH1TiqJvb3NEgYmSW6Cpbdm.svg
1188 ms
thK2GxrHmob02b0oYQr5YysOY07t2zQAlFr42DUz.svg
1424 ms
33e5xOBLCckq8QBA60BQmHQE1BesWYskmTyZmiro.png
2144 ms
m0UEvvIdDOiCVqLZxNyPLrRM7duImOvU6ElH8JE1.png
1832 ms
GBzVgPIrB7kapAGiyt37D7DvDWDGg00vZlzZTfP1.png
2144 ms
JuQt3WHjyqu4mksRDGFAOaeo5mrlmazQuZ3Tg9Lv.png
2263 ms
REq5yFs6tzCDtBwo8KiP4kQ1ofKU6RCYYpRaRLgr.png
2286 ms
xcau7g4VQjXLazw8eSOlG5b0XYO1OKwqBEQdU4Va.png
2580 ms
DAUtugwyGzKQ3znZIfGwPDWoFZofJgn1E0F9TTbH.png
2434 ms
wFBDqVNBZcSAABMgXJc0wAw90uf7o70HBYhgpzaZ.png
2479 ms
9YuUNcKFOgt8cL0C9RxMrZ6PfFKd6QmMVIUa0ubR.png
2518 ms
cxcl6pdlxtI5otV9zY7n80E3DbjrXOLw1873PmwR.png
2659 ms
vqa2bE864Eg0zbCHxue66mTtzkk1kR2eFOtIpnqt.png
2707 ms
t287rGssitsdoCdYdhhZjstM0wG2RguF5kJiN5po.png
2729 ms
CcOR7xMBUMyNPTlrVJAFSpLKlR8n6ppA2N8Z1ivG.png
2748 ms
lBGBemMSo68BPbE3XakXIYqRahcyTPM8tVPlvzxq.jpg
2813 ms
eTIBG08p2c2kvfRBAYXpTEm2faEuw1l2ePldFPd7.png
3108 ms
hucAQxu4eReKA3GoJcm0OX9SUVm9Sj8Y2nJF34h6.jpg
2930 ms
AH8ZTUyTCsQgyrdDQIYxdujQQ8KelwG3MHd8BhTF.png
2980 ms
b7qVnXCVYVtrLqBc7wdiTrisY3UtHbjALtxe9Soi.jpg
2978 ms
gWh4sahX3U8N6laNu9Ir44LOzbugaX3RenTA9YxB.png
2988 ms
vQxvi8d9jYw9glelh4srpj0CJFxXN5FPNSk1XsOr.png
3279 ms
no8csX8D7Y78whbGokaC3WgpRMRsHZz89A9TS8K8.png
3159 ms
1CtAyiyWSYGures1nZPAGDvMfphjU1GeXXFsLfqE.png
4537 ms
BQ2MNyVqxNQF05OFAmsTREOpyMf2MfRiEe2QfaO1.png
3204 ms
nAZGG17GlvpWUvcsNdPMOcPTyeySM5H5ExtZZ4ZP.png
3224 ms
m3uSma6UFn3EIwv5lB4BeGn1s6zmjX2nHIyPCJsO.jpg
3332 ms
i43OC6I3bVt4QedzHAldlKyPIR8t7PBhIZfgylkZ.jpg
3390 ms
B1P0vL9Wr9pDgnLsnghXhDqGzX8635buDUwmPSXH.jpg
3438 ms
CwXixOH6MnOy3c75RoUveQrg516XK9nSBDdZqMN9.jpg
3679 ms
logo.svg
669 ms
nav-grid-icon.svg
868 ms
SG1.svg
874 ms
SG2.svg
891 ms
timeline-decor.svg
897 ms
jquery.min.js
1333 ms
moment.min.js
20 ms
daterangepicker.min.js
20 ms
sweetalert2@11
31 ms
app-fce26334.js
1304 ms
carousel-f1c6e967.js
1536 ms
select2.js
1772 ms
select2-id.js
1122 ms
facebook.svg
1351 ms
instagram.svg
2201 ms
twitter.svg
1554 ms
linkedin.svg
1580 ms
youtube.svg
1756 ms
logo-kominfo.svg
2234 ms
contact_support.svg
1808 ms
css2
34 ms
css2
52 ms
wsCMOhVPdeOukABcJylvJcKZF8f0xNyLgrKyHtZV.png
2563 ms
g5LFYHZRlLU8y6ePXmM11vb8c5PxSrb2V3oqmYmu.png
2370 ms
BKRKHLYcj1Q26VDHnwuMPS7X1v4zYn1RrIUYtuWN.png
2196 ms
Ghvz79mXF3XGGpc7P4RdcMOII8GrXk2oaRKgPBTF.png
2072 ms
6qkuVhOhnLayncs0iaTDjzfvysLZo3k8Xz4dbObQ.png
1920 ms
1hrpq0h27bFvLVJeCvMgixEwsWSVzuNoKEAUB1qz.png
1635 ms
yLKGI9eTai0Nu2vcJ0FfFO3dpSRZ9RqFgNlpgOAx.png
1701 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZthTg.ttf
31 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxhTg.ttf
40 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxhTg.ttf
61 ms
fa-solid-900-8d25a104.ttf
915 ms
fa-regular-400-caad7e4d.ttf
223 ms
fa-light-300-ba80ae06.ttf
1110 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat-JDW3z.ttf
79 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat-7DW3z.ttf
80 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat9uCm3z.ttf
79 ms
QBWz6KRH15RD1MZOhbsM3YxnjQ8KHm9jIsm0tLRO.png
1758 ms
boPFikQSXgPDXUq8rUI9M8KTwe2nsg9ROSLLVmfL.png
1687 ms
kiUfZw9qYHqMhAdfBHcFLpXSqHktEXT2LmzmgKyQ.png
1724 ms
mEhxxcViJZH768YTuWpOTYsPjfPiQyry1UKT5HNr.jpg
1718 ms
f2d6jRvhJajyv4asT1snMJ8vbAbyaT6VczbT2iYl.png
1637 ms
6TZPif1RdJZenAUyMCDyJPKMgYkDCwlnobViK9ap.png
1652 ms
hub.id accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
hub.id 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hub.id 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hub.id 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 Hub.id 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.
hub.id
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: