Tools & Wizards About Us
webtrains.net screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

webtrains.net

Web Trains : l'information ferroviaire

Page Load Speed

2.4 sec in total

First Response

500 ms

Resources Loaded

1.7 sec

Page Rendered

193 ms

webtrains.net screenshot

About Website

Welcome to webtrains.net homepage info - get ready to check Web Trains best content right away, or after learning these important things about webtrains.net

L'actualité ferroviaire de référence avec Web Trains, votre locomotive de l'information pour suivre le train du monde entier.

Visit webtrains.net

Key Findings

We analyzed Webtrains.net page load time and found that the first response time was 500 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

webtrains.net performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

webtrains.net

500 ms

ga.js

19 ms

show_ads.js

70 ms

2018.jpg

373 ms

3.gif

271 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 34% of them (15 requests) were addressed to the original Webtrains.net, 20% (9 requests) were made to Img.locotrain.com and 11% (5 requests) were made to Tech.webtrains.net. The less responsive or slowest element that took the longest time to load (768 ms) relates to the external source Img.locotrain.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.9 kB (13%)

Content Size

543.6 kB

After Optimization

474.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Webtrains.net main page is 543.6 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. 25% of websites need less resources to load. Javascripts take 273.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 62.2 kB

  • Original 79.7 kB
  • After minification 77.9 kB
  • After compression 17.6 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 62.2 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 6.7 kB

  • Original 190.1 kB
  • After minification 183.5 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. Web Trains images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 121 B

  • Original 273.8 kB
  • After minification 273.8 kB
  • After compression 273.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 14 (35%)

Requests Now

40

After Optimization

26

  • AJAX
  • Images
  • JavaScript

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Web Trains. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

webtrains.net

webtrains.net

500 ms

ga.js

ga.js

19 ms

show_ads.js

show_ads.js

70 ms

2018.jpg

2018.jpg

373 ms

3.gif

3.gif

271 ms

content_copyrightfrance.gif

content_copyrightfrance.gif

254 ms

logo.gif

logo.gif

252 ms

corne.gif

corne.gif

251 ms

menu.gif

menu.gif

251 ms

form.gif

form.gif

252 ms

point.gif

point.gif

251 ms

ico_rss.gif

ico_rss.gif

249 ms

ico_fav.gif

ico_fav.gif

330 ms

ico_blog.gif

ico_blog.gif

323 ms

ico_mb.gif

ico_mb.gif

321 ms

2754.jpg

2754.jpg

495 ms

2030.jpg

2030.jpg

588 ms

5136.jpg

5136.jpg

687 ms

3736.jpg

3736.jpg

588 ms

5377.jpg

5377.jpg

698 ms

__utm.gif

__utm.gif

12 ms

adsbygoogle.js

adsbygoogle.js

107 ms

t_h1.gif

t_h1.gif

245 ms

t_h2.gif

t_h2.gif

244 ms

m_h1.gif

m_h1.gif

245 ms

5136.jpg

5136.jpg

716 ms

menu_bottom.gif

menu_bottom.gif

337 ms

point_bottom.gif

point_bottom.gif

336 ms

3736.jpg

3736.jpg

548 ms

2018.jpg

2018.jpg

768 ms

show_ads_impl.js

show_ads_impl.js

322 ms

zrt_lookup.html

zrt_lookup.html

45 ms

ads

ads

362 ms

ads

ads

341 ms

ads

ads

307 ms

ads

ads

111 ms

fr_468x60_tradedoubler.php

fr_468x60_tradedoubler.php

180 ms

fr_160x600_tradedoubler.php

fr_160x600_tradedoubler.php

155 ms

fr_160x600_tradedoubler.php

fr_160x600_tradedoubler.php

264 ms

thalys.gif

thalys.gif

315 ms

ouigo.gif

ouigo.gif

247 ms

db.gif

db.gif

307 ms

1030346

1030346

129 ms

1030346

1030346

128 ms

Accessibility Review

webtrains.net accessibility score

69

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

webtrains.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

webtrains.net SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webtrains.net 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 Webtrains.net 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.

Social Sharing Optimization

webtrains.net

Open Graph description is not detected on the main page of Web Trains. 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: