3.5 sec in total
333 ms
2.7 sec
424 ms
Welcome to raildar.fr homepage info - get ready to check Raildar best content for France right away, or after learning these important things about raildar.fr
Visit raildar.frWe analyzed Raildar.fr page load time and found that the first response time was 333 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
raildar.fr performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value10.0 s
0/100
25%
Value8.1 s
21/100
10%
Value300 ms
78/100
30%
Value0.001
100/100
15%
Value9.4 s
31/100
10%
333 ms
19 ms
191 ms
165 ms
182 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 59% of them (60 requests) were addressed to the original Raildar.fr, 39% (40 requests) were made to Otile2.mqcdn.com and 2% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Otile2.mqcdn.com.
Page size can be reduced by 1.3 MB (61%)
2.1 MB
810.7 kB
In fact, the total size of Raildar.fr main page is 2.1 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 23.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 23.8 kB or 79% of the original size.
Potential reduce by 25.0 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. Raildar images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 84% of the original size.
Potential reduce by 138.4 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. Raildar.fr needs all CSS files to be minified and compressed as it can save up to 138.4 kB or 82% of the original size.
Number of requests can be reduced by 48 (48%)
100
52
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raildar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
raildar.fr
333 ms
font-awesome.css
19 ms
bootstrap.min.css
191 ms
jquery.jqplot.css
165 ms
leaflet.css
182 ms
jquery-ui-1.10.3.custom.css
188 ms
jquery-ui-timepicker-addon.css
182 ms
raildar.css
206 ms
leaflet.js
333 ms
leaflet-hash.js
313 ms
jquery-2.0.3.js
453 ms
underscore-min.js
313 ms
jquery.jqplot.js
554 ms
jqplot.pieRenderer.js
328 ms
bootstrap.min.js
408 ms
bootbox.js
405 ms
moment.min.js
427 ms
moment.fr.js
412 ms
handlebars.js
589 ms
handlebars-helpers.js
505 ms
handlebars-util.js
505 ms
library.js
522 ms
Static.js
540 ms
Filters.js
603 ms
DataSource.js
603 ms
TrainDataSource.js
623 ms
DataSourceConfig.js
632 ms
Trains.js
639 ms
InfoLigne.js
678 ms
Trajet.js
678 ms
Stats.js
681 ms
Scheduler.js
719 ms
Tracking.js
724 ms
DisplayManager.js
731 ms
StatsDisplay.js
759 ms
TrainDisplay.js
765 ms
FiltersDisplay.js
771 ms
jquery-ui-1.10.3.custom.min.js
907 ms
jquery-ui-timepicker-addon.js
670 ms
train_loading.gif
648 ms
train_full.png
673 ms
fontawesome-webfont.woff
4 ms
MainWorker.js
140 ms
TrackingWorker.js
134 ms
spark-md5.min.js
171 ms
22.png
113 ms
22.png
48 ms
21.png
50 ms
21.png
102 ms
23.png
92 ms
23.png
37 ms
22.png
79 ms
22.png
53 ms
21.png
90 ms
21.png
79 ms
23.png
135 ms
23.png
110 ms
20.png
162 ms
20.png
157 ms
24.png
117 ms
24.png
129 ms
20.png
275 ms
20.png
201 ms
22.png
158 ms
22.png
205 ms
24.png
229 ms
24.png
397 ms
21.png
199 ms
21.png
231 ms
23.png
260 ms
23.png
289 ms
20.png
355 ms
20.png
394 ms
24.png
354 ms
24.png
1215 ms
22.png
378 ms
22.png
421 ms
21.png
660 ms
21.png
414 ms
23.png
435 ms
23.png
499 ms
layers.png
92 ms
20.png
490 ms
20.png
438 ms
24.png
475 ms
moment.min.js
97 ms
24.png
455 ms
moment.fr.js
92 ms
underscore.js
97 ms
library.js
93 ms
Static.js
93 ms
WorkerConsole.js
92 ms
DataSource.js
92 ms
TrainDataSource.js
93 ms
DataSourceConfig.js
92 ms
get_circulation
94 ms
fleche_green.png
92 ms
fleche_orange.png
93 ms
fleche_yellow.png
89 ms
fleche_red.png
93 ms
fleche_black.png
94 ms
fleche_blue.png
102 ms
raildar.fr accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
raildar.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
Browser errors were logged to the console
Page has valid source maps
raildar.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 doesn't use legible font sizes
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Raildar.fr can be misinterpreted by Google and other search engines. Our service has detected that French 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 Raildar.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.
raildar.fr
Open Graph description is not detected on the main page of Raildar. 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: