5.8 sec in total
672 ms
4.8 sec
312 ms
Visit handigo.fr now to see the best up-to-date Handigo content and also check out these interesting facts you probably never knew about handigo.fr
Retrouvez tous les services bus, tram'bus et vélo de l'agglomération de Nîmes : calculateur d'itinéraires conseillés, actualités, horaires aux arrêts, plans... Retrouvez toutes les informations dont v...
Visit handigo.frWe analyzed Handigo.fr page load time and found that the first response time was 672 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
handigo.fr performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value5.0 s
27/100
25%
Value8.0 s
22/100
10%
Value350 ms
73/100
30%
Value0.007
100/100
15%
Value12.5 s
14/100
10%
672 ms
273 ms
352 ms
572 ms
1195 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Handigo.fr, 24% (12 requests) were made to Static.tango.cityway.fr and 4% (2 requests) were made to Cdn.smartly.ai. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Tangobus.fr.
Page size can be reduced by 203.3 kB (14%)
1.5 MB
1.2 MB
In fact, the total size of Handigo.fr main page is 1.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. 30% of websites need less resources to load. Images take 990.8 kB which makes up the majority of the site volume.
Potential reduce by 67.6 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 16.1 kB, which is 20% 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 67.6 kB or 83% of the original size.
Potential reduce by 135.1 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, Handigo needs image optimization as it can save up to 135.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 390 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 229 B
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. Handigo.fr has all CSS files already compressed.
Number of requests can be reduced by 5 (11%)
47
42
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Handigo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
www.tangobus.fr
672 ms
site-638470448200000000.css
273 ms
LinesColor-v638521056000000000.css
352 ms
logo.svg
572 ms
Base-vendor-638470448200000000.js
1195 ms
Base-638470448200000000.js
846 ms
script-638470448200000000.js
443 ms
bundle-638470448200000000.js
664 ms
logo-print.png
572 ms
tripplanner.svg
708 ms
schedules.svg
721 ms
plans.svg
724 ms
e-shop.svg
755 ms
logo-transdev-nimes.svg
801 ms
logo-nimes-metropole.svg
812 ms
couv-site-montez-validez.png
1511 ms
actu-orange.png
435 ms
actu-site-360x210.jpg
1421 ms
actu-tangomobile-rentree-2023.png
626 ms
actu-dessertes-etablissements-sco-2023-3-.png
724 ms
actu-nouveautes-rentree-2023.png
813 ms
fb-paloma-rentree2023.png
997 ms
actu-trafic-semaine-2.png
1182 ms
background.svg
1058 ms
select-arrow.svg
1058 ms
transinfo.woff
1453 ms
adobeblank.woff
2619 ms
gothamrounded-bold.woff
2361 ms
webchat.min.js
283 ms
displaydisruptionsinset
900 ms
getdisruptedlinegroups
346 ms
puce-t2-bd.png
94 ms
puce-6-bd.png
94 ms
puce-9-bd.png
186 ms
ligne11bd.jpg
276 ms
puce-15bd.png
279 ms
ligne20bd.jpg
363 ms
ligne43bd.jpg
443 ms
puce-51bd.png
371 ms
puce-52bd.png
527 ms
ligne73bd.jpg
535 ms
ligne-tempo-214bd.jpg
630 ms
ligne-tempo-222bd.jpg
649 ms
ligne-tempo-227bd.jpg
721 ms
ligne-tempo-231bd.jpg
738 ms
802-1.png
723 ms
802-2.png
745 ms
tempo-230.JPG
816 ms
print-638470448200000000.css
99 ms
Base-accessibility-638470448200000000.js
93 ms
whitecloseicon.png
109 ms
handigo.fr 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
handigo.fr 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
handigo.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Handigo.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Handigo.fr 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.
handigo.fr
Open Graph data is detected on the main page of Handigo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: