8.9 sec in total
2.4 sec
6.2 sec
268 ms
Click here to check amazing Oogolo content. Otherwise, check out these important facts you probably never knew about oogolo.com
Tous les voyages, comparer les prix des vols, des locations. La Bible du voyageur malin
Visit oogolo.comWe analyzed Oogolo.com page load time and found that the first response time was 2.4 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
oogolo.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.3 s
69/100
25%
Value11.9 s
4/100
10%
Value2,830 ms
3/100
30%
Value0.011
100/100
15%
Value20.0 s
2/100
10%
2375 ms
1834 ms
176 ms
349 ms
188 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Oogolo.com, 26% (15 requests) were made to Static.liligo.com and 24% (14 requests) were made to Cdn.oogolo.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Oogolo.com.
Page size can be reduced by 578.6 kB (56%)
1.0 MB
460.6 kB
In fact, the total size of Oogolo.com 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. 55% of websites need less resources to load. Javascripts take 394.3 kB which makes up the majority of the site volume.
Potential reduce by 40.3 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 40.3 kB or 80% of the original size.
Potential reduce by 84 B
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. Oogolo images are well optimized though.
Potential reduce by 260.7 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 260.7 kB or 66% of the original size.
Potential reduce by 277.5 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. Oogolo.com needs all CSS files to be minified and compressed as it can save up to 277.5 kB or 83% of the original size.
Number of requests can be reduced by 27 (54%)
50
23
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oogolo. 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 from 9 to 1 for CSS and as a result speed up the page load time.
oogolo.com
2375 ms
www.oogolo.fr
1834 ms
bootstrap.min.css
176 ms
v3.css
349 ms
default.1458061531.css
188 ms
css
58 ms
logo.png
1066 ms
1164 ms
1168 ms
1172 ms
jquery-2.1.4.min.js
270 ms
bootstrap.min.js
187 ms
scriptsV3.js
425 ms
dojo.js
425 ms
default.1458074990.js
259 ms
280x187.jpg
1134 ms
280x187.jpg
1051 ms
280x187.jpg
1139 ms
280x187.jpg
1140 ms
280x187.jpg
1146 ms
280x187.jpg
1221 ms
280x187.jpg
1221 ms
280x187.jpg
1220 ms
280x187.jpg
1227 ms
280x187.jpg
1227 ms
280x187.jpg
1326 ms
280x187.jpg
1392 ms
logo_footer.png
1306 ms
ga.js
37 ms
uYKcPVoh6c5R0NpdEY5A-Q.woff
36 ms
DXI1ORHCpsQm3Vp6mXoaTRsxEYwM7FgeyaSgU71cLG0.woff
69 ms
k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff
82 ms
EInbV5DfGHOiMmvb1Xr-hhsxEYwM7FgeyaSgU71cLG0.woff
82 ms
fontawesome-webfont.woff
174 ms
glyphicons-halflings-regular.woff
107 ms
full.js
532 ms
FrontendHP
236 ms
searchbox.css
233 ms
form.css
234 ms
basecss.css
252 ms
full.js
600 ms
FrontendHP
229 ms
form.css
253 ms
full.js
482 ms
form.css
309 ms
full.js
572 ms
datepicker.gif
102 ms
submit.png
97 ms
hdots_transparent.gif
99 ms
datepicker-sprites.png
184 ms
error-msg-bg.png
193 ms
error-msg-bg.png
88 ms
gray-triangle.gif
86 ms
vdots.gif
98 ms
clock.gif
98 ms
comparesite-bg.png
100 ms
comparesite-bg.png
79 ms
comploc-icons.png
180 ms
oogolo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
oogolo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
oogolo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
FR
FR
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oogolo.com 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 Oogolo.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
oogolo.com
Open Graph description is not detected on the main page of Oogolo. 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: