11.8 sec in total
265 ms
10.3 sec
1.2 sec
Click here to check amazing Vsct content for France. Otherwise, check out these important facts you probably never knew about vsct.fr
Visit vsct.frWe analyzed Vsct.fr page load time and found that the first response time was 265 ms and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
vsct.fr performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value20.4 s
0/100
25%
Value12.3 s
3/100
10%
Value3,610 ms
1/100
30%
Value0.001
100/100
15%
Value23.6 s
1/100
10%
265 ms
428 ms
128 ms
94 ms
95 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Vsct.fr, 44% (24 requests) were made to Voyages-sncf.com and 9% (5 requests) were made to T.voyages-sncf.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Gum.criteo.com.
Page size can be reduced by 134.1 kB (55%)
245.1 kB
111.0 kB
In fact, the total size of Vsct.fr main page is 245.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 147.1 kB which makes up the majority of the site volume.
Potential reduce by 282 B
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 282 B or 50% of the original size.
Potential reduce by 12.3 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, Vsct needs image optimization as it can save up to 12.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 96.0 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 96.0 kB or 65% of the original size.
Potential reduce by 25.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. Vsct.fr needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 85% of the original size.
Number of requests can be reduced by 28 (62%)
45
17
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vsct. 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 7 to 1 for CSS and as a result speed up the page load time.
vsct.fr
265 ms
structureVSCT.htm
428 ms
canvas-final.min.css
128 ms
css_injector_153.css
94 ms
css_injector_246.css
95 ms
css_injector_263.css
87 ms
css_4b543d3fff6aa7969c371f97c080ee3e.css
203 ms
css-class.min.js
140 ms
js_59528cedecae8885a94fdbce21c979ba.jsmin.js
316 ms
canvas.min.js
137 ms
js_9bf38a568848fab84b1eb1c038de8f4e.jsmin.js
542 ms
background-noise.png
281 ms
voyages-sncf-fr-FR.png
273 ms
b.gif
277 ms
voyages-sncf--white.png
266 ms
menu_icon_75557.jpg
265 ms
menu_icon_75558.png
262 ms
all.js
263 ms
errors-background-1.png
270 ms
sprites-booking-8.png
276 ms
stripes-dark-grey.png
270 ms
sprites-booking-4.png
283 ms
stripes-green.png
269 ms
vsca.js
1988 ms
2
1744 ms
405595.js
1734 ms
iadvize.js
903 ms
cityList.js
371 ms
last-searches.html
353 ms
1YAAQAAAAAAAQAAAADG1C6ZAAAAALklKMIAAAAAuSUowg==
53 ms
9bGYwYsAAALMIB6gA=
52 ms
+EA4QMhFOEiwTABNqE8YXuBgUGFgYhhkaGmwa3BuuHJgdxB5cIBghZiGKIdYiUCLQIx4j+iSmJSwlaiYUJoYnWifMKK4peCoiKr4rdCv2LGIs0gAAAAEAAABMAs4ACwAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAOAK4AAQAAAAAAAQADAAAAAQAAAAAAAgAHADwAAQAAAAAAAwADACoAAQAAAAAABAADAFEAAQAAAAAABQALAAkAAQAAAAAABgADADMAAQAAAAAACgAaAFoAAwABBAkAAQAGAAMAAwABBAkAAgAOAEMAAwABBAkAAwAGAC0AAwABBAkABAAGAFQAAwABBAkABQAWABQAAwABBAkABgAGADYAAwABBAkACgA0AHRWU0MAVgBTAENWZXJzaW9uIDEuMABWAGUAcgBzAGkAbwBuACAAMQAuADBWU0MAVgBTAENWU0MAVgBTAENSZWd1bGFyAFIAZQBnAHUAbABhAHJWU0MAVgBTAENGb250IGdlbmVyYXRlZCBieSBJY29Nb29uLgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
51 ms
avenirltstd-roman-webfont.woff
52 ms
wACK7EDRnYrRLAQIEW6AA8BYwACK7EDRnYrRLARIEWyEFoCK7EDRnYrRLASIEWyEUsCK7EDRnYrRLATIEWyEiACK7EDRnYrRFmwFCsAAAA=
49 ms
nc2635.js
197 ms
station-finder-1-c90d13f82630da679131d00b349bd5fb.js
790 ms
station-finder-1-c3c3f00e4dc5fff09640fc7e3f6a1160.css
1111 ms
leaflet-ie8.css
371 ms
1221 ms
storage.local.php
601 ms
1835879318
172 ms
s_code.prd.js
236 ms
pixel
982 ms
2335a9ceefa21.js
1046 ms
sync
3066 ms
realytics.js
354 ms
cnktZzZkOXhlMGx8cnlfMjJFNzM5M0YtMzBGRS00MTRGLTlGQTMtNEJEQ0E0ODc4QjU4fA%3D%3D
598 ms
pixel
36 ms
681 ms
426 ms
pix1x1.gif
206 ms
xd_arbiter.php
2232 ms
xd_arbiter.php
2597 ms
id
475 ms
xd_arbiter.php
358 ms
vsct.fr 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
[role]s are not contained by their required parent element
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
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.
vsct.fr 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
vsct.fr SEO score
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
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vsct.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Vsct.fr 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.
vsct.fr
Open Graph description is not detected on the main page of Vsct. 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: