4.5 sec in total
248 ms
3.9 sec
289 ms
Click here to check amazing Aix En Bus content for France. Otherwise, check out these important facts you probably never knew about aixenbus.fr
Réseau de La Métropole Mobilité qui dessert les communes d'Aix-en-Provence, Éguilles, Le Tholonet, Saint-Marc-Jaumegarde et Venelles.
Visit aixenbus.frWe analyzed Aixenbus.fr page load time and found that the first response time was 248 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
aixenbus.fr performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.3 s
69/100
25%
Value3.8 s
83/100
10%
Value0 ms
100/100
30%
Value0.002
100/100
15%
Value3.3 s
93/100
10%
248 ms
1175 ms
30 ms
12 ms
275 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 95% of them (53 requests) were addressed to the original Aixenbus.fr, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Motoka-ws.ctp.prod.canaltp.fr. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Aixenbus.fr.
Page size can be reduced by 602.2 kB (58%)
1.0 MB
438.6 kB
In fact, the total size of Aixenbus.fr main page is 1.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. 35% of websites need less resources to load. Javascripts take 519.2 kB which makes up the majority of the site volume.
Potential reduce by 69.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 25.7 kB, which is 31% 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 69.7 kB or 85% of the original size.
Potential reduce by 32.9 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. Aix En Bus images are well optimized though.
Potential reduce by 400.5 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 400.5 kB or 77% of the original size.
Potential reduce by 99.0 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. Aixenbus.fr needs all CSS files to be minified and compressed as it can save up to 99.0 kB or 84% of the original size.
Number of requests can be reduced by 36 (67%)
54
18
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aix En Bus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
aixenbus.fr
248 ms
www.aixenbus.fr
1175 ms
ga.js
30 ms
__utm.gif
12 ms
global.css
275 ms
specific.css
286 ms
jquery-ui-1.8.17.custom.css
290 ms
ctp_urbain_common.css
198 ms
jquery.bookmark.css
203 ms
ctp.css
221 ms
firstletter.css
296 ms
ctp_tools.css
305 ms
1133 ms
ezcategoryselection.js
226 ms
FormControler.js
259 ms
jquery-1.7.1.min.js
675 ms
jquery-ui-1.8.17.custom.min.js
495 ms
jquery.easing.1.3.js
312 ms
jquery.easing.compatibility.js
307 ms
modernizr.custom.36771.js
339 ms
plugins.js
440 ms
scripts.js
410 ms
box-info.js
411 ms
ctp.js
452 ms
base.js
511 ms
conversion.js
513 ms
proj4js-combined.js
1091 ms
jquery.bookmark.js
564 ms
bg-body.png
113 ms
bg-global.png
195 ms
bg-header.jpg
1028 ms
s-interface.png
783 ms
tel.jpg
103 ms
ico-en.png
125 ms
ico-fr.png
207 ms
logo.png
479 ms
bg-navmain-cur.gif
218 ms
Reseau-Aix-en-Bus_large.png
672 ms
Application-mobile-Aix-en-Bus_large.jpg
1343 ms
bg-titre.gif
308 ms
bg-form-trajets.gif
402 ms
bg-input.png
493 ms
ico-star.png
590 ms
deco-fl.png
585 ms
ico-calendar-default.png
677 ms
encart-map.jpg
1246 ms
spacer.png
772 ms
logo-keolis.png
771 ms
le+pilote.png
863 ms
aller_bd-webfont.woff
1433 ms
icons-home.png
1145 ms
s-info.png
931 ms
bg-footer.gif
1023 ms
inimo.png
1096 ms
bg-li.png
1115 ms
ui-bg_flat_75_ffffff_40x100.png
1131 ms
aixenbus.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.
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
<object> elements do not have alternate text
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
aixenbus.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
aixenbus.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Aixenbus.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 Aixenbus.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.
aixenbus.fr
Open Graph data is detected on the main page of Aix En Bus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: