3.8 sec in total
474 ms
2.4 sec
883 ms
Click here to check amazing Hublo content for France. Otherwise, check out these important facts you probably never knew about hublo.com
Un outil simple et ergonomique pour gérer ses remplacements et recrutements de soignants en toute simplicité.
Visit hublo.comWe analyzed Hublo.com page load time and found that the first response time was 474 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
hublo.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value5.9 s
14/100
25%
Value4.5 s
72/100
10%
Value270 ms
82/100
30%
Value0.06
98/100
15%
Value10.0 s
27/100
10%
474 ms
328 ms
54 ms
75 ms
125 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 52% of them (24 requests) were addressed to the original Hublo.com, 35% (16 requests) were made to Images.prismic.io and 2% (1 request) were made to Js.hs-scripts.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Hublo.com.
Page size can be reduced by 335.2 kB (50%)
674.1 kB
338.9 kB
In fact, the total size of Hublo.com main page is 674.1 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. 60% of websites need less resources to load. HTML takes 384.4 kB which makes up the majority of the site volume.
Potential reduce by 333.8 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 333.8 kB or 87% of the original size.
Potential reduce by 1.4 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. Hublo images are well optimized though.
Number of requests can be reduced by 11 (28%)
39
28
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hublo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
en
474 ms
fonts.css
328 ms
2369852.js
54 ms
collectedforms.js
75 ms
2369852.js
125 ms
conversations-embed.js
87 ms
2369852.js
117 ms
842de47.js
13 ms
e3b7076.js
25 ms
5bff7e9.js
298 ms
e218098.js
80 ms
191053a.js
63 ms
0677f11.js
38 ms
gtm.js
224 ms
78262417-f235-4d04-b983-d59f18769505_hospital_photo_homepage_website.jpg
188 ms
cross-hero.d5b2fd1.webp
159 ms
shape-bg.aea755a.svg
414 ms
shape-dash-red.a15466c.svg
149 ms
shape-blue.432044d.svg
146 ms
shape-dash-blue.fac9fd0.svg
147 ms
shape-green.dee0739.svg
436 ms
round-bg.828af78.webp
436 ms
dotted-bg.4a7e5f4.svg
402 ms
shape-red.e4d79ad.svg
156 ms
cta-bg.23d4669.webp
474 ms
3cc5e48d-4c52-4bb5-a0e6-52bd97d4dfb7_clinic_photo_homepage_website.jpg
175 ms
fcfb9863-c750-4f89-9a09-9c3a6d0f18fe_ehpad_photo_homepage_website.jpg
193 ms
e332d943-6b53-43e3-9ba3-cc8526295ccf_logo_chu_brest.jpg
200 ms
fcc9baa7-07ad-4568-93ad-3e43126433e4_Icon+sun.svg
198 ms
d308c55f-37a6-471f-9c0b-4ee74183a0ea_icon+users.svg
197 ms
d15e8251-b70f-4b4d-ad4b-787044303d6c_Icon+lightning.svg
207 ms
15025287-fb10-4894-805b-0de8e7343dcf_icon+integration.svg
193 ms
7a6ab663-eb42-4953-9637-bae8196197a2_Face8.png
199 ms
737ff094-1ca4-44da-a8b8-e1139c92fcef_Face2.png
206 ms
fd9bad4d-4e51-4d03-8536-6f7b0535b04b_Face6.png
205 ms
b49f9028-108f-436f-ba54-7556a053bdc1_Face7.png
208 ms
3067d007-75b5-445d-85a8-573d8c4a589f_Face4.png
206 ms
3b3068b9-952b-48fa-8ccb-d772ad39b8c4_Face3.png
205 ms
8e6ee14d-a463-49c7-b9be-f1a7142fcaaf_Face1.png
208 ms
9275178b-227e-49c5-9c3e-5e16f73e4f1e_image+avec+tuile.png
209 ms
Geomanist-Medium.otf
455 ms
geomanist-regular-webfont.woff
919 ms
Nunito-Regular.ttf
783 ms
Nunito-Light.ttf
1123 ms
Nunito-SemiBold.ttf
1107 ms
Nunito-Bold.ttf
860 ms
hublo.com 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.
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
Links do not have a discernible name
hublo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hublo.com SEO score
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 Hublo.com 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 Hublo.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.
hublo.com
Open Graph description is not detected on the main page of Hublo. 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: