2.1 sec in total
142 ms
1.6 sec
389 ms
Visit downtownorlando.com now to see the best up-to-date Downtown Orlando content for United States and also check out these interesting facts you probably never knew about downtownorlando.com
Visit downtownorlando.comWe analyzed Downtownorlando.com page load time and found that the first response time was 142 ms and then it took 2 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.
downtownorlando.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value12.0 s
0/100
25%
Value6.7 s
36/100
10%
Value1,000 ms
27/100
30%
Value0.119
84/100
15%
Value12.6 s
14/100
10%
142 ms
11 ms
19 ms
33 ms
16 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 71% of them (46 requests) were addressed to the original Downtownorlando.com, 8% (5 requests) were made to Cdnjs.cloudflare.com and 8% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Api.worldweatheronline.com.
Page size can be reduced by 577.4 kB (40%)
1.4 MB
869.4 kB
In fact, the total size of Downtownorlando.com main page is 1.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. 70% of websites need less resources to load. Images take 970.0 kB which makes up the majority of the site volume.
Potential reduce by 37.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 8.6 kB, which is 19% 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 37.5 kB or 81% of the original size.
Potential reduce by 219.3 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, Downtown Orlando needs image optimization as it can save up to 219.3 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 116.9 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 116.9 kB or 63% of the original size.
Potential reduce by 203.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. Downtownorlando.com needs all CSS files to be minified and compressed as it can save up to 203.8 kB or 83% of the original size.
Number of requests can be reduced by 26 (44%)
59
33
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Downtown Orlando. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.downtownorlando.com
142 ms
bootstrap.min.css
11 ms
bootstrap-responsive.min.css
19 ms
font-awesome.min.css
33 ms
clingify.css
16 ms
css
39 ms
ddb-styles.css
21 ms
ddb-responsive-styles.css
30 ms
magnific-popup.min.css
36 ms
jquery.min.js
42 ms
bootstrap.min.js
33 ms
jquery.easing.min.js
33 ms
jquery.min.js
39 ms
jquery.clingify.min.js
24 ms
wp-embed.min.js
37 ms
wp-emoji-release.min.js
95 ms
weather.ashx
1213 ms
cse.js
68 ms
ga.js
69 ms
ddb-logo.png
17 ms
twitter-icon.png
16 ms
facebook-icon.png
18 ms
youtube-icon.png
15 ms
instagram-icon.png
17 ms
pinterest-icon.png
17 ms
random-image2.jpg
204 ms
welcome-downtown.png
18 ms
live-40x40.png
19 ms
play-40x40.png
18 ms
eat-40x40.png
19 ms
shop-40x40.png
200 ms
stay-40x40.png
199 ms
dto-circle.png
198 ms
map.png
199 ms
twitter-dto.png
200 ms
facebook-dto.png
199 ms
youtube-dto.png
200 ms
instagram-dto.png
201 ms
pinterest-dto.png
201 ms
Parking-Graphic-02-5.jpg
202 ms
DOP-Homepage.jpeg
208 ms
sunrail2.jpg
202 ms
ddb-transportation.png
201 ms
neighborhoods.png
204 ms
ddb-info.png
204 ms
ddb-socialize.png
202 ms
ddb-parking.png
202 ms
ddb-calendar.png
203 ms
showcase-bg.jpg
204 ms
38-special-240x175.png
204 ms
BaBa%E2%80%99s-Orlando-Mediterranean-Restaurant-2.png
212 ms
icon_search.png
205 ms
cse.js
215 ms
__utm.gif
27 ms
frabk-webfont.svg
121 ms
frabk-webfont.woff
40 ms
montserrat-regular-webfont.svg
40 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
22 ms
montserrat-bold-webfont.svg
38 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
37 ms
jsapi
58 ms
default+en.css
3 ms
default.css
44 ms
default+en.I.js
15 ms
default.css
17 ms
downtownorlando.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
downtownorlando.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
downtownorlando.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Downtownorlando.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 Downtownorlando.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.
downtownorlando.com
Open Graph description is not detected on the main page of Downtown Orlando. 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: