Tools & Wizards About Us
churchstreetdistrict.com screenshot

Report Summary

  • 0

    Performance

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

churchstreetdistrict.com

Church Street Orlando: Guide to Church Street Station

Page Load Speed

7.6 sec in total

First Response

262 ms

Resources Loaded

4.8 sec

Page Rendered

2.5 sec

churchstreetdistrict.com screenshot

About Website

Visit churchstreetdistrict.com now to see the best up-to-date Church Street District content for United States and also check out these interesting facts you probably never knew about churchstreetdistrict.com

Discover the charm of Church Street Orlando. Find top dining spots, attractions, events, and local history. Your essential guide to Church Street Station.

Visit churchstreetdistrict.com

Key Findings

We analyzed Churchstreetdistrict.com page load time and found that the first response time was 262 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

churchstreetdistrict.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.603

10/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

churchstreetdistrict.com

262 ms

www.churchstreetdistrict.com

531 ms

bootstrap.min.css

144 ms

flaticon.css

175 ms

mega_menu.css

182 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 51% of them (44 requests) were addressed to the original Churchstreetdistrict.com, 28% (24 requests) were made to Fonts.gstatic.com and 11% (10 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Churchstreetdistrict.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.6 kB (14%)

Content Size

819.3 kB

After Optimization

705.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Churchstreetdistrict.com main page is 819.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 355.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 24.4 kB

  • Original 30.9 kB
  • After minification 25.3 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 5.6 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.4 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 2.3 kB

  • Original 355.9 kB
  • After minification 353.6 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. Church Street District images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 38.1 kB

  • Original 313.6 kB
  • After minification 313.6 kB
  • After compression 275.5 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 38.1 kB or 12% of the original size.

CSS Optimization

-41%

Potential reduce by 48.8 kB

  • Original 118.9 kB
  • After minification 117.4 kB
  • After compression 70.1 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. Churchstreetdistrict.com needs all CSS files to be minified and compressed as it can save up to 48.8 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (69%)

Requests Now

58

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

churchstreetdistrict.com

churchstreetdistrict.com

262 ms

www.churchstreetdistrict.com

www.churchstreetdistrict.com

531 ms

bootstrap.min.css

bootstrap.min.css

144 ms

flaticon.css

flaticon.css

175 ms

mega_menu.css

mega_menu.css

182 ms

font-awesome.min.css

font-awesome.min.css

190 ms

owl.carousel.css

owl.carousel.css

203 ms

magnific-popup.css

magnific-popup.css

205 ms

settings.css

settings.css

222 ms

style.css

style.css

342 ms

responsive.css

responsive.css

247 ms

adsbygoogle.js

adsbygoogle.js

2487 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

304 ms

popper.js

popper.js

237 ms

bootstrap.min.js

bootstrap.min.js

258 ms

mega_menu.js

mega_menu.js

262 ms

jquery.appear.js

jquery.appear.js

303 ms

jquery.countTo.js

jquery.countTo.js

332 ms

owl.carousel.min.js

owl.carousel.min.js

332 ms

jquery-select.js

jquery-select.js

645 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

645 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

646 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

649 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

646 ms

revolution.extension.carousel.min.js

revolution.extension.carousel.min.js

703 ms

revolution.extension.kenburn.min.js

revolution.extension.kenburn.min.js

696 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

698 ms

revolution.extension.migration.min.js

revolution.extension.migration.min.js

695 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

695 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

972 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

971 ms

revolution.extension.video.min.js

revolution.extension.video.min.js

971 ms

custom.js

custom.js

971 ms

css

css

22 ms

css

css

47 ms

embed

embed

706 ms

embed

embed

320 ms

church-street-district.png

church-street-district.png

596 ms

church-street-station.jpg

church-street-station.jpg

1074 ms

01.jpg

01.jpg

1569 ms

02.jpg

02.jpg

1372 ms

kcuvee-wine-education.jpg

kcuvee-wine-education.jpg

733 ms

kres-chophouse.jpg

kres-chophouse.jpg

733 ms

sak-comedy-lab.jpg

sak-comedy-lab.jpg

917 ms

disney-vip-tours.jpg

disney-vip-tours.jpg

917 ms

mad-cow-theatre.jpg

mad-cow-theatre.jpg

1072 ms

best-of.jpg

best-of.jpg

1267 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

376 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

408 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

467 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

466 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

466 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

518 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLDrMfJQ.ttf

518 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJQ.ttf

523 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMDrMfJQ.ttf

521 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf

522 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJQ.ttf

521 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDrMfJQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDrMfJQ.ttf

523 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1000 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

521 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

59 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

641 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

196 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

629 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

299 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

617 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

298 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

617 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

344 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

774 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

344 ms

flag.js

flag.js

966 ms

js

js

399 ms

gen_204

gen_204

130 ms

init_embed.js

init_embed.js

223 ms

common.js

common.js

282 ms

util.js

util.js

246 ms

map.js

map.js

223 ms

overlay.js

overlay.js

173 ms

onion.js

onion.js

104 ms

search_impl.js

search_impl.js

105 ms

openhand_8_8.cur

openhand_8_8.cur

324 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

69 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

191 ms

vt

vt

217 ms

vt

vt

215 ms

Accessibility Review

churchstreetdistrict.com accessibility score

63

Accessibility Issues

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

Document doesn't have a <title> element

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

Best Practices

churchstreetdistrict.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

churchstreetdistrict.com SEO score

55

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

Document doesn't have a <title> element

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 Churchstreetdistrict.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 Churchstreetdistrict.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

churchstreetdistrict.com

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