17.1 sec in total
507 ms
10.4 sec
6.2 sec
Welcome to rauto.be homepage info - get ready to check Rauto best content right away, or after learning these important things about rauto.be
Visit rauto.beWe analyzed Rauto.be page load time and found that the first response time was 507 ms and then it took 16.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rauto.be performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value7.7 s
3/100
25%
Value15.5 s
0/100
10%
Value280 ms
81/100
30%
Value0.673
8/100
15%
Value14.2 s
9/100
10%
507 ms
158 ms
113 ms
1473 ms
1054 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 63% of them (39 requests) were addressed to the original Rauto.be, 24% (15 requests) were made to Secure.pic.autoscout24.net and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Secure.pic.autoscout24.net.
Page size can be reduced by 2.4 MB (46%)
5.2 MB
2.8 MB
In fact, the total size of Rauto.be main page is 5.2 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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 57.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. This page needs HTML code to be minified as it can gain 12.0 kB, which is 17% 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 57.3 kB or 82% of the original size.
Potential reduce by 108.8 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. Rauto images are well optimized though.
Potential reduce by 923.1 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 923.1 kB or 71% of the original size.
Potential reduce by 1.3 MB
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. Rauto.be needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 86% of the original size.
Number of requests can be reduced by 28 (54%)
52
24
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rauto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
rauto.be
507 ms
rauto.be
158 ms
Default.aspx
113 ms
Home.aspx
1473 ms
html5reset.css
1054 ms
col.css
1054 ms
2cols.css
864 ms
3cols.css
941 ms
4cols.css
942 ms
5cols.css
833 ms
6cols.css
866 ms
7cols.css
650 ms
8cols.css
650 ms
9cols.css
1545 ms
10cols.css
1137 ms
11cols.css
1488 ms
12cols.css
1124 ms
bootstrap.min.css
1107 ms
bootstrap-glyphicons.css
1105 ms
css
1514 ms
css
2687 ms
css
1961 ms
jquery.cookiebar.css
1944 ms
jquery-1.7.1.min.js.download
1447 ms
jquery.cookiebar.js.download
1841 ms
jquery-latest.min.js
1390 ms
font-awesome.min.css
2854 ms
menumaker.min.js
2805 ms
script.js
1942 ms
WebResource.axd
1942 ms
ScriptResource.axd
2602 ms
ScriptResource.axd
2600 ms
simpleslide.css
2599 ms
jquerysctipttop.css
1558 ms
simpleslide.js
2372 ms
jquery.min.js
2373 ms
bootstrap.min.js
2373 ms
scripts.js
2373 ms
0326265022001.jpg
4399 ms
homepage_cars.jpg
657 ms
homepage_tradein.jpg
598 ms
homepage_contact.jpg
1852 ms
homepage_freepage.jpg
649 ms
autoscout24_logo.gif
640 ms
0326264660001.jpg
4323 ms
0325966093001.jpg
4754 ms
0325785371001.jpg
4954 ms
0325784894001.jpg
4740 ms
0325203531001.jpg
4738 ms
0324634186001.jpg
4564 ms
0324483314001.jpg
4564 ms
0324200116001.jpg
4640 ms
0324191551001.jpg
4656 ms
0311351757001.jpg
5039 ms
0311262037001.jpg
5063 ms
0308793955001.jpg
5063 ms
0305444496001.jpg
5039 ms
0300644024001.jpg
5064 ms
none
1230 ms
arrow-left.gif
1000 ms
arrow-right.gif
1000 ms
fontawesome-webfont.woff
1027 ms
rauto.be 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Links do not have a discernible name
rauto.be 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
Browser errors were logged to the console
Page has valid source maps
rauto.be 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
Image elements do not have [alt] attributes
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
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rauto.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rauto.be main page’s claimed encoding is . 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.
rauto.be
Open Graph description is not detected on the main page of Rauto. 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: