8.6 sec in total
3.5 sec
4.9 sec
157 ms
Click here to check amazing Tickets Amtrak content for United States. Otherwise, check out these important facts you probably never knew about tickets.amtrak.com
Book your Amtrak train and bus tickets today by choosing from over 30 U.S. train routes and 500 destinations in North America.
Visit tickets.amtrak.comWe analyzed Tickets.amtrak.com page load time and found that the first response time was 3.5 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tickets.amtrak.com performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value64.1 s
0/100
25%
Value25.4 s
0/100
10%
Value13,950 ms
0/100
30%
Value0.647
9/100
15%
Value79.8 s
0/100
10%
3542 ms
20 ms
258 ms
36 ms
34 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 63% of them (56 requests) were addressed to the original Tickets.amtrak.com, 20% (18 requests) were made to Amtrak.com and 7% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Tickets.amtrak.com.
Page size can be reduced by 1.1 MB (75%)
1.5 MB
372.9 kB
In fact, the total size of Tickets.amtrak.com main page is 1.5 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. 50% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 74.1 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 74.1 kB or 81% of the original size.
Potential reduce by 10.2 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, Tickets Amtrak needs image optimization as it can save up to 10.2 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 761.8 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 761.8 kB or 74% of the original size.
Potential reduce by 293.3 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. Tickets.amtrak.com needs all CSS files to be minified and compressed as it can save up to 293.3 kB or 86% of the original size.
Number of requests can be reduced by 48 (57%)
84
36
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tickets Amtrak. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
amtrak
3542 ms
amtrak.css
20 ms
base.css
258 ms
base_screen.css
36 ms
topnav.css
34 ms
basic_booking.css
584 ms
special_booking.css
259 ms
basic_booking_screen.css
38 ms
ib_misc.css
37 ms
popup.css
40 ms
profile.css
53 ms
amtrak_autocomplete.css
51 ms
satelliteLib-073129b141b5f91c45cd8781dde0bb81599a5e0e.js
220 ms
header.css
50 ms
prototype.js
73 ms
scriptaculous.js
71 ms
effects.js
71 ms
controls.js
114 ms
formutils.js
73 ms
popups.js
82 ms
profile_rewrite.js
82 ms
farefinderrequest.js
106 ms
header.js
97 ms
motionpoint.js
118 ms
jquery-1.11.2.min.js
128 ms
base.js
124 ms
basic_booking_left.js
126 ms
amtrak-calendar.css
128 ms
jquery-ui.min.js
184 ms
moment.js
172 ms
jquery.comiseo.daterangepicker.js
133 ms
datepicker.js
150 ms
jquery-ui.css
173 ms
jquery.comiseo.daterangepicker.css
181 ms
datepicker.css
180 ms
webtrends_session.js
193 ms
NIT.Embed.js
143 ms
adrum-latest.js
36 ms
ga.js
80 ms
ijm4cfl.js
151 ms
Satellite
348 ms
btn_closeXorange.gif
39 ms
btn_ff_findTrains.gif
138 ms
btn_checkStatus.gif
139 ms
btn_find.gif
139 ms
btn_login.gif
65 ms
btn_continue.gif
65 ms
Satellite
316 ms
Satellite
315 ms
Satellite
316 ms
Satellite
346 ms
Satellite
325 ms
DisplayCmsContent
411 ms
__utm.gif
16 ms
ffTabs_All.png
61 ms
ffTabs_BuyOptions.gif
61 ms
bullet_triangleBlue.gif
341 ms
ffCalendar.png
340 ms
info_icon.gif
341 ms
subheading1_reservationoptions.gif
98 ms
dcs.gif
40 ms
tickets.amtrak.com
56 ms
JRF68rmS41m1Bs02XaVCLbzv0u532ishd-1YB8kn3a6ff4nygsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
42 ms
XGgsakqoUdVIvCRabGrpMw4um-NhcwUEKDiGddNKdd3ff4DygsMdeMJ6Mk6g5MZfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
72 ms
1wutm3DDy-U8MXba3pD-ZZQeFlSLVR_JTduLVowspNSff4_ygsMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
102 ms
-v95iBv14ccJdWF-yPjHzWOGsHCZZwWd0ORkrKZvlWqff4zygsMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
122 ms
s-code-contents-daccfff5b17f965441732dec484a92f9d5777e9e.js
51 ms
p.gif
144 ms
s58330784658901
7 ms
Satellite
66 ms
Satellite
37 ms
Satellite
39 ms
Satellite
48 ms
Satellite
68 ms
Satellite
40 ms
Satellite
104 ms
Satellite
104 ms
Satellite
105 ms
Satellite
58 ms
Satellite
204 ms
Satellite
68 ms
logo_header.png
42 ms
icon_questionMarkInfo-header.png
80 ms
icon_globe.png
76 ms
background_header.png
78 ms
triangle_AGRdown.png
39 ms
nav_downPointer.png
39 ms
basic_booking_print.css
74 ms
base_print.css
32 ms
tickets.amtrak.com 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
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[role] values are not valid
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
tickets.amtrak.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tickets.amtrak.com 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tickets.amtrak.com 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 Tickets.amtrak.com 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.
tickets.amtrak.com
Open Graph description is not detected on the main page of Tickets Amtrak. 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: