Tools & Wizards About Us

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

trolleycar.net

Chicago Trolley Rental - The Trolley Car & Bus Company

Page Load Speed

1.6 sec in total

First Response

143 ms

Resources Loaded

1.1 sec

Page Rendered

356 ms

About Website

Click here to check amazing Trolley Car content. Otherwise, check out these important facts you probably never knew about trolleycar.net

Rent a trolley in Chicago for weddings, special events, corporate outings, groups and more through The Trolley Car & Bus Company.

Visit trolleycar.net

Key Findings

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

Performance Metrics

trolleycar.net performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

trolleycar.net

143 ms

trolleycar.net

282 ms

js

64 ms

style.min.css

105 ms

astra-theme-dynamic-css-post-85.css

160 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 81% of them (42 requests) were addressed to the original Trolleycar.net, 12% (6 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (458 ms) belongs to the original domain Trolleycar.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.9 kB (8%)

Content Size

992.2 kB

After Optimization

909.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trolleycar.net main page is 992.2 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. 60% of websites need less resources to load. Images take 523.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 67.6 kB

  • Original 84.1 kB
  • After minification 81.2 kB
  • After compression 16.5 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 67.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 150 B

  • Original 523.3 kB
  • After minification 523.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. Trolley Car images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 14.2 kB

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

CSS Optimization

-0%

Potential reduce by 1.1 kB

  • Original 222.7 kB
  • After minification 222.7 kB
  • After compression 221.7 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. Trolleycar.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (88%)

Requests Now

41

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

trolleycar.net accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

trolleycar.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

trolleycar.net SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Trolleycar.net 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 Trolleycar.net 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

Open Graph data is detected on the main page of Trolley Car. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: