2.7 sec in total
100 ms
2.2 sec
301 ms
Welcome to downtownicesj.com homepage info - get ready to check Downtownicesj best content for United States right away, or after learning these important things about downtownicesj.com
Visit downtownicesj.comWe analyzed Downtownicesj.com page load time and found that the first response time was 100 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
downtownicesj.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.2 s
72/100
25%
Value4.8 s
67/100
10%
Value20 ms
100/100
30%
Value0.059
98/100
15%
Value4.6 s
81/100
10%
100 ms
98 ms
108 ms
72 ms
77 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Downtownicesj.com, 38% (40 requests) were made to Static.parastorage.com and 18% (19 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (781 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.8 MB (62%)
4.5 MB
1.7 MB
In fact, the total size of Downtownicesj.com main page is 4.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. 80% 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. Javascripts take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 91.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 91.5 kB or 83% of the original size.
Potential reduce by 65.1 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. Downtownicesj images are well optimized though.
Potential reduce by 2.5 MB
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 2.5 MB or 75% of the original size.
Potential reduce by 114.0 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. Downtownicesj.com needs all CSS files to be minified and compressed as it can save up to 114.0 kB or 85% of the original size.
Number of requests can be reduced by 64 (67%)
96
32
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Downtownicesj. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
downtownicesj.com
100 ms
www.downtownicesj.com
98 ms
bt
108 ms
require.min.js
72 ms
main-r.min.js
77 ms
viewer.css
76 ms
dynamicmodel
17 ms
7e52be_ec3034d18f423736fc8daddcb5b32172_383.json.z
607 ms
7e52be_87d13e056e469bac29ac2d4839badd5c_383.json.z
429 ms
ugc-viewer
52 ms
bt
114 ms
skins.min.js
103 ms
components.min.js
102 ms
utils.min.js
38 ms
core.min.js
398 ms
react-with-addons.min.js
96 ms
lodash.min.js
86 ms
TweenMax.min.js
94 ms
layout.min.js
88 ms
tpa.min.js
97 ms
fonts.min.js
95 ms
animations.min.js
94 ms
swfobject.min.js
93 ms
mousetrap.min.js
92 ms
tweenEngine.min.js
96 ms
DrawSVGPlugin.min.js
96 ms
react-dom.min.js
95 ms
ScrollToPlugin.min.js
94 ms
widgets.min.js
90 ms
experiment.js
372 ms
render.min.js
371 ms
wixappsCore.min.js
375 ms
wixappsBuilder.min.js
371 ms
zepto.min.js
373 ms
color.min.js
372 ms
react-dom-server.min.js
194 ms
bt
194 ms
bt
365 ms
dc.js
356 ms
7e52be_5ee02608859840e3a58d14afeca93c41.jpg
295 ms
latin.css
120 ms
googleMap.html
128 ms
StripSlideshow.html
126 ms
7e52be_04d38b012fce4da99d8fe0b8644442f7.jpg
248 ms
30646eb34311104aba036a018b9a226b.png
221 ms
d090c1c8997ee76d531500a6002f81a2.png
92 ms
d3645e6fa159b8ef24374656fc7b245a.png
90 ms
7e52be_761cfa852bf04ababca954acd4d5b858.png
355 ms
7e52be_9af4c3278fa242eb94e24c27c736f7a1.png
506 ms
84770f_76d8ec58322e440e88e09eb4fb6f8582.jpg
389 ms
7e52be_89433c9688064a5faa2db3761eb1a76f.jpg
506 ms
7e52be_7f6daa37e3ea48e3b21f053d8e2e9b4c.jpg
352 ms
7e52be_2db5b42e93b944328417c7a69375a8d1.png
669 ms
7e52be_049a09c17cda4b9ca727df76eb5a650c.jpg
504 ms
7e52be_e0e7eb687cb94fb8813ee98e4ffdb4a7.jpg
666 ms
7e52be_25e11cfc515b49a680a779f70cd990fc.jpg
669 ms
7e52be_ca6fc6c293a04d1ab163eb1568c3c213.jpg
781 ms
bt
78 ms
bt
77 ms
bt
224 ms
jquery.min.js
82 ms
jquery.easing-1.3.min.js
76 ms
lodash.min.js
208 ms
webfont.js
244 ms
Wix.js
407 ms
style.min.css
216 ms
app.min.js
77 ms
js
244 ms
__utm.gif
26 ms
8fb1090e-b4d0-4685-ac8f-3d0c29d60130.woff
156 ms
opensans-regular-webfont.woff
39 ms
opensans-bold-webfont.woff
154 ms
f84b539d-ed34-4400-a139-c0f909af49aa.woff
154 ms
common.js
55 ms
map.js
76 ms
util.js
109 ms
marker.js
75 ms
StaticMapService.GetMapImage
297 ms
ugc-viewer
63 ms
onion.js
20 ms
openhand_8_8.cur
196 ms
ViewportInfoService.GetViewportInfo
111 ms
stats.js
110 ms
controls.js
106 ms
infowindow.js
105 ms
css
161 ms
spotlight-poi.png
89 ms
transparent.png
104 ms
google4.png
61 ms
mapcnt6.png
61 ms
vt
47 ms
vt
40 ms
vt
40 ms
vt
44 ms
vt
39 ms
vt
59 ms
vt
53 ms
tmapctrl.png
38 ms
cb_scout5.png
42 ms
tmapctrl4.png
47 ms
imgs8.png
47 ms
AuthenticationService.Authenticate
14 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
20 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
27 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
31 ms
downtownicesj.com accessibility score
downtownicesj.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
downtownicesj.com SEO score
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 Downtownicesj.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 Downtownicesj.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.
downtownicesj.com
Open Graph description is not detected on the main page of Downtownicesj. 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: