Your Website Score is

Similar Ranking

37
ABEMATV|国内最大の無料インターネットテレビ局
abema.tv
37
ATTENTION REQUIRED! | CLOUDFLARE
jang.com.pk
37
WIX SUPPORT
support.wix.com
37
ATTENTION REQUIRED! | CLOUDFLARE
vitalsource.com
37
SHAREASALE
shareasale.com
37
401 AUTHORIZATION REQUIRED
sankakucomplex.com
37
M2NEWMEDIA.COM IS COMING SOON
m2newmedia.com

Latest Sites

31
ネットセキュリティブログ
japan-secure.com
48
JAIST 北陸先端科学技術大学院大学
jaist.ac.jp
32
IPOD(アイポッド)の使い方ガイド | IPOD WAVE
ipodwave.com
43
HTMLコーディングの代行・外注はクロノドライブ
html-coding.co.jp
32
FXをもっとやさしく「みんなのFX」|みんなのFX
min-fx.jp

Top Technologies

Nginx
Web Servers
Google Font API
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
CloudFlare
CDN
WordPress
CMS
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks

37 trainline.fr Last Updated: 1 week

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 78%
Best Practices Desktop Score 62%
SEO Desktop Score 91%
Progressive Web App Desktop Score 27%
Performance Mobile Score 48%
Best Practices Mobile Score 69%
SEO Mobile Score 78%
Progressive Web App Mobile Score 33%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 71 Characters
BILLETS DE TRAIN ET HORAIRES | RéSERVEZ EN FRANCE ET EUROPE | TRAINLINE
Meta Description 156 Characters
Réservez vos billets de train pour voyager en France et dans plus de 30 pays européens. Comparez les horaires de train et les prix avec Trainline.
Effective URL 24 Characters
Excerpt Page content
Billets de train et Horaires | Réservez en France et Europe | Trainline ...
Keywords Cloud Density
pour15 billets15 paris13 trainline13 vous11 train11 notre8 trains8 nous8 prix6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
pour 15
billets 15
paris 13
trainline 13
vous 11
train 11
notre 8
trains 8
nous 8
prix 6
Google Preview Your look like this in google search result
BILLETS DE TRAIN ET HORAIRES | RéSERVEZ EN FRANCE ET EUROPE
https://www.trainline.fr
Réservez vos billets de train pour voyager en France et dans plus de 30 pays européens. Comparez les horaires de train et les prix avec Trai
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~85.81 KB
Code Size: ~66.03 KB
Text Size: ~19.78 KB Ratio: 23.05%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Avoids an excessive DOM size 639 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 136 requests • 2,212 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 440 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 3.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 17.2 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 110 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 68 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 113 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Server response times are low (TTFB) Root document took 210 ms
Time To First Byte identifies the time at which your server sends a response
Reduce the impact of third-party code Third-party code blocked the main thread for 250 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 480 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Defer offscreen images Potential savings of 413 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 3.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,212 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Mobile

Mobile Screenshot
Minimize main-thread work 8.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoids an excessive DOM size 315 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 103 requests • 996 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 6 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,400 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 11.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Page load is not fast enough on mobile networks Interactive at 11.7 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 3660 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 730 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Tap targets are not sized appropriately 33% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Serve images in next-gen formats Potential savings of 9 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Server response times are low (TTFB) Root document took 500 ms
Time To First Byte identifies the time at which your server sends a response
Reduce the impact of third-party code Third-party code blocked the main thread for 2,030 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Total Blocking Time 4,430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 6.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Defer offscreen images Potential savings of 10 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 2 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 5.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 10.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 996 KB
Large network payloads cost users real money and are highly correlated with long load times

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html
Last-Modified: Thu, 28 Nov 2019 14:43:21 GMT
ETag: "e7d8577d09962e147b70c2739dc7aa8c"
Accept-Ranges: bytes
Strict-Transport-Security: max-age=16070400; includeSubDomains; preload
Content-Security-Policy: frame-ancestors https://www.thetrainline.com https://www.liligo.fr
Cache-Control: no-cache, no-store
Vary: Accept-Language
Vary: Accept-Encoding
Content-Encoding: gzip
Date: Mon, 02 Dec 2019 01:50:05 GMT
Content-Length: 20
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments