Tools & Wizards About Us
sightseeingtrains.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

sightseeingtrains.com

Ripley’s Red Train Tours, St. Augustine | Tickets, hours

Page Load Speed

1.8 sec in total

First Response

39 ms

Resources Loaded

1.3 sec

Page Rendered

492 ms

sightseeingtrains.com screenshot

About Website

Click here to check amazing Sightseeing Train S content. Otherwise, check out these important facts you probably never knew about sightseeingtrains.com

Wind through the historic streets of St. Augustine, FL on your narrated adventure at the Ripley’s Red Train Tours. More than 100 historical points of interest.

Visit sightseeingtrains.com

Key Findings

We analyzed Sightseeingtrains.com page load time and found that the first response time was 39 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

sightseeingtrains.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

redtrains

39 ms

wp-emoji-release.min.js

14 ms

formidablepro.css

36 ms

style.css

23 ms

spring.css

14 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sightseeingtrains.com, 5% (4 requests) were made to Static.tacdn.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (318 ms) relates to the external source Ripleys.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.0 kB (7%)

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sightseeingtrains.com main page is 2.4 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. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.1 kB

  • Original 52.8 kB
  • After minification 52.6 kB
  • After compression 9.7 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 43.1 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 108.8 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Sightseeing Train S images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 1.3 kB

  • Original 49.6 kB
  • After minification 49.6 kB
  • After compression 48.4 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.

CSS Optimization

-79%

Potential reduce by 6.8 kB

  • Original 8.6 kB
  • After minification 7.0 kB
  • After compression 1.8 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. Sightseeingtrains.com needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (58%)

Requests Now

77

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

redtrains

redtrains

39 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

14 ms

formidablepro.css

formidablepro.css

36 ms

style.css

style.css

23 ms

spring.css

spring.css

14 ms

nivo-slider.css

nivo-slider.css

14 ms

tip-twitter.css

tip-twitter.css

34 ms

tip-yellowsimple.css

tip-yellowsimple.css

32 ms

prettyPhoto.css

prettyPhoto.css

41 ms

superfish-custom.css

superfish-custom.css

40 ms

jquery.tabs.css

jquery.tabs.css

42 ms

jquery.js

jquery.js

49 ms

jquery-migrate.min.js

jquery-migrate.min.js

43 ms

custom.js

custom.js

42 ms

jqueryui.js

jqueryui.js

42 ms

easing.js

easing.js

43 ms

jquery.cycle.all.js

jquery.cycle.all.js

45 ms

quicksand.js

quicksand.js

45 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

43 ms

jquery.poshytip.min.js

jquery.poshytip.min.js

47 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

48 ms

superfish.js

superfish.js

47 ms

supersubs.js

supersubs.js

47 ms

jquery.tabs.pack.js

jquery.tabs.pack.js

53 ms

jquery.history_remote.pack.js

jquery.history_remote.pack.js

48 ms

cufon-yui.js

cufon-yui.js

52 ms

bebas-neue.font.js

bebas-neue.font.js

59 ms

output.css

output.css

51 ms

hoverIntent.min.js

hoverIntent.min.js

51 ms

qppr_frontend_script.min.js

qppr_frontend_script.min.js

53 ms

reset.css

reset.css

40 ms

nggallery.css

nggallery.css

45 ms

ga.js

ga.js

24 ms

canvas.jpg

canvas.jpg

54 ms

RT_bg.jpg

RT_bg.jpg

66 ms

nav-arrow.png

nav-arrow.png

57 ms

redTrainTours-logo.png

redTrainTours-logo.png

57 ms

slideshow-border-top.png

slideshow-border-top.png

58 ms

slideshow-border-bottom.png

slideshow-border-bottom.png

57 ms

slideshow-border-bg.png

slideshow-border-bg.png

57 ms

loading.gif

loading.gif

318 ms

BOGO-staugustine-redtrainslider1.png

BOGO-staugustine-redtrainslider1.png

81 ms

promoSlider61.jpg

promoSlider61.jpg

74 ms

promoSlider22.jpg

promoSlider22.jpg

92 ms

Redtrain-1daytickets-slider.jpg

Redtrain-1daytickets-slider.jpg

94 ms

St.JohnPromo-RedTrainwebsite1.png

St.JohnPromo-RedTrainwebsite1.png

92 ms

getTickets.png

getTickets.png

106 ms

St-Augustine-your-way.png

St-Augustine-your-way.png

103 ms

more-button.png

more-button.png

105 ms

thumb-bg.png

thumb-bg.png

107 ms

footer-bg.png

footer-bg.png

157 ms

bottom-bg.png

bottom-bg.png

123 ms

follow-bg.png

follow-bg.png

113 ms

facebook_16.png

facebook_16.png

114 ms

twitter_16.png

twitter_16.png

123 ms

footer-separator.png

footer-separator.png

123 ms

wejs

wejs

107 ms

__utm.gif

__utm.gif

21 ms

collect

collect

61 ms

WidgetEmbed-certificateOfExcellence

WidgetEmbed-certificateOfExcellence

52 ms

ga-audiences

ga-audiences

50 ms

cdswidCOE-v21462574883a.css%20%27%29%3B

cdswidCOE-v21462574883a.css%20%27%29%3B

4 ms

cdswidFRR-v23865805545a.css%20%27%29%3B

cdswidFRR-v23865805545a.css%20%27%29%3B

4 ms

cdswidgets_min-c-v23892882724a.js

cdswidgets_min-c-v23892882724a.js

32 ms

cdswidCOE-v21462574883a.css

cdswidCOE-v21462574883a.css

29 ms

cdswidFRR-v23865805545a.css

cdswidFRR-v23865805545a.css

30 ms

prev-slide.png

prev-slide.png

11 ms

next-slide.png

next-slide.png

10 ms

slidebutton-over.png

slidebutton-over.png

15 ms

slidebutton.png

slidebutton.png

15 ms

lazyload.1.0.2.min.js

lazyload.1.0.2.min.js

14 ms

nr-100.js

nr-100.js

17 ms

roundtrip.js

roundtrip.js

109 ms

CoE2015_WidgetAsset-14348-2.png

CoE2015_WidgetAsset-14348-2.png

11 ms

BackgroundRuleBlack.gif

BackgroundRuleBlack.gif

8 ms

b98da38656

b98da38656

46 ms

photoGallery.jpg

photoGallery.jpg

21 ms

exploreTheRoute.jpg

exploreTheRoute.jpg

21 ms

EventsCalendar.jpg

EventsCalendar.jpg

19 ms

ripleysBION.png

ripleysBION.png

8 ms

ghostTrain.png

ghostTrain.png

12 ms

vendor_discounts.png

vendor_discounts.png

9 ms

BestOf_2014-StAugustine-400px.png

BestOf_2014-StAugustine-400px.png

23 ms

Accessibility Review

sightseeingtrains.com accessibility score

73

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sightseeingtrains.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

sightseeingtrains.com SEO score

83

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sightseeingtrains.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sightseeingtrains.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.

Social Sharing Optimization

sightseeingtrains.com

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