downtownla.com

downtownla.com is SSL secured

Free website and domain report on downtownla.com

Last Updated: 14th August, 2023 Update Now
Overview

Snoop Summary for downtownla.com

This is a free and comprehensive report about downtownla.com. The domain downtownla.com is currently hosted on a server located in United States with the IP address 75.2.44.162, where the local currency is USD and English is the local language. Our records indicate that downtownla.com is owned/operated by Downtown Center Business Improve Dist Mgm. Downtownla.com has the potential to be earning an estimated $4 USD per day from advertising revenue. If downtownla.com was to be sold it would possibly be worth $3,187 USD (based on the daily revenue potential of the website over a 24 month period). Downtownla.com receives an estimated 1,527 unique visitors every day - a large amount of traffic! This report was last updated 14th August, 2023.

About downtownla.com

Site Preview: downtownla.com downtownla.com
Title: Downtown LA
Description: DowntownLA.com is proudly brought to you by the Downtown Center BID, a coalition of property owners committed to enhancing the quality of life in the Downtown Center.
Keywords and Tags: ca, los angeles, public information
Related Terms: downtown, downtown kitchener, downtown victoria bc, downtown victoria canada
Fav Icon:
Age: Over 27 years old
Domain Created: 11th July, 1996
Domain Updated: 4th February, 2022
Domain Expires: 10th July, 2031
Review

Snoop Score

2/5

Valuation

$3,187 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 534,146
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,527
Monthly Visitors: 46,477
Yearly Visitors: 557,355
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $132 USD
Yearly Revenue: $1,588 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: downtownla.com 14
Domain Name: downtownla 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.57 seconds
Load Time Comparison: Faster than 47% of sites

PageSpeed Insights

Avg. (All Categories) 87
Performance 98
Accessibility 100
Best Practices 83
SEO 100
PWA 56
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://downtownla.com/
Updated: 21st September, 2022

1.08 seconds
First Contentful Paint (FCP)
92%
5%
3%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for downtownla.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://downtownla.com/
http/1.1
0
131.04999996722
263
0
301
text/html
https://downtownla.com/
h2
131.35099993087
326.22499996796
7535
31362
200
text/html
Document
https://ctycms.com/ca-dtla/css/cty_css_v21.min.css
h2
332.56099978462
455.85799985565
26206
173289
200
text/css
Stylesheet
https://downtownla.com/_templates/_styles.css?v=12f
h2
332.67399994656
405.39699979126
13828
80565
200
text/css
Stylesheet
https://use.typekit.net/ezz3lth.css
h2
332.86099997349
357.93399997056
1323
6144
200
text/css
Stylesheet
https://kit.fontawesome.com/1872c177cb.js
h2
457.0909999311
500.0089998357
4639
11075
200
text/javascript
Script
https://ctycms.com/ca-dtla/footer-logo-2.svg
h2
463.80499983206
554.83299982734
2589
6807
200
image/svg+xml
Image
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
h2
406.52699978091
520.23699996062
55935
174019
200
application/javascript
Script
https://jscloud.net/x/5147/inlinks.js
h2
463.95699982531
497.13599984534
673
0
200
application/javascript
Script
https://p.typekit.net/p.css?s=1&k=ezz3lth&ht=tk&f=10879.10881.10884.10887.15586.39182.39184.39187&a=519809&app=typekit&e=css
h2
359.37600000761
384.237999795
336
5
200
text/css
Stylesheet
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
h2
464.10999982618
504.80599980801
54348
168604
200
application/javascript
Script
https://acdn.adnxs.com/dmp/up/pixie.js
http/1.1
464.25799978897
484.43899978884
3928
9139
200
application/javascript
Script
https://use.typekit.net/af/5c4f69/00000000000000007735bbfb/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
h2
469.31699989364
499.2659999989
72006
71688
200
application/font-woff2
Font
https://use.typekit.net/af/309dfe/000000000000000000010091/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
h2
469.55499984324
496.62399990484
43394
43076
200
application/font-woff2
Font
https://use.typekit.net/af/bdd682/00000000000000007735bbe9/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
h2
484.96699985117
515.76999993995
71954
71636
200
application/font-woff2
Font
https://use.typekit.net/af/0c71d1/000000000000000000010097/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n8&v=3
h2
485.11599982157
511.13399979658
40862
40544
200
application/font-woff2
Font
https://use.typekit.net/af/cfc06a/00000000000000007735bbef/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i4&v=3
h2
487.57999995723
516.85599982738
78218
77900
200
application/font-woff2
Font
https://img.ctykit.com/cdn/ca-dtla/docs/dcbid-looping-video-final-1080.mov
507.64399999753
1387.1109997854
0
0
-1
Media
https://ib.adnxs.com/pixie?e=PageView&pi=7a67b1cc-7f17-4ff1-a0e7-0f4075b2113b&it=1663790213221&v=0.0.20&u=https%3A%2F%2Fdowntownla.com%2F&st=1663790213221&et=1663790213222&if=0
http/1.1
541.35699989274
820.17999980599
347
42
200
image/gif
Image
https://www.google-analytics.com/analytics.js
h2
582.62299979106
590.52399988286
20451
49672
200
text/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
h2
586.55699994415
599.91299989633
28106
103160
200
application/x-javascript
Script
https://ka-p.fontawesome.com/releases/v6.2.0/css/pro.min.css?token=1872c177cb
h2
588.51899998263
686.31699983962
173956
807028
200
text/css
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/css/pro-v5-font-face.min.css?token=1872c177cb
h2
588.72399991378
616.07999983244
12839
85987
200
text/css
Fetch
https://www.google-analytics.com/j/collect?v=1&_v=j97&a=14912236&t=pageview&_s=1&dl=https%3A%2F%2Fdowntownla.com%2F&ul=en-us&de=UTF-8&dt=Downtown%20LA&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAAABAAAAAC~&jid=1942805241&gjid=935929481&cid=1964607439.1663790213&tid=UA-69671207-1&_gid=753517.1663790213&_r=1&gtm=2wg9j052H452&z=1431215367
h2
615.65499985591
625.68699987605
613
2
200
text/plain
XHR
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
h2
635.00999985263
757.21999979578
87077
299390
200
application/x-javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j97&tid=UA-69671207-1&cid=1964607439.1663790213&jid=1942805241&gjid=935929481&_gid=753517.1663790213&_u=YEBAAAAAAAAAAC~&z=303460524
h2
636.9279997889
647.19799999148
685
1
200
text/plain
XHR
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/home-things-dining-2022.jpg
h2
637.12599989958
723.58599980362
59649
59074
200
image/webp
Image
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/bottega-louie-2.jpg
h2
637.27999990806
733.63799997605
76618
76042
200
image/webp
Image
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/home-things-shop-2022.jpg
h2
637.50999979675
752.55299988203
151187
150610
200
image/webp
Image
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-brands-400-f6b769.woff2
h2
759.31599992327
792.44299978018
18876
18440
200
font/woff2
Font
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-brands-400-9b80fe.woff2
h2
759.47599997744
783.51599979214
45874
45440
200
font/woff2
Font
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-solid-900-51b08f.woff2
h2
759.73099982366
784.77899986319
27675
27240
200
font/woff2
Font
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-solid-900-50c900.woff2
h2
759.85499983653
788.68699981831
28491
28056
200
font/woff2
Font
https://www.facebook.com/tr/?id=275012842862574&ev=PageView&dl=https%3A%2F%2Fdowntownla.com%2F&rl=&if=false&ts=1663790213484&sw=800&sh=600&v=2.9.83&r=stable&ec=0&o=30&fbp=fb.1.1663790213482.710675578&it=1663790213315&coo=false&rqm=GET
h2
803.22399991564
814.6720000077
478
44
200
image/gif
Image
https://www.facebook.com/tr/?id=275012842862574&ev=Microdata&dl=https%3A%2F%2Fdowntownla.com%2F&rl=&if=false&ts=1663790213988&cd[DataLayer]=%5B%5D&cd[Meta]=%7B%22title%22%3A%22Downtown%20LA%22%2C%22meta%3Adescription%22%3A%22DowntownLA.com%20is%20proudly%20brought%20to%20you%20by%20the%20Downtown%20Center%20BID%2C%20a%20coalition%20of%20property%20owners%20committed%20to%20enhancing%20the%20quality%20of%20life%20in%20the%20Downtown%20Center.%22%2C%22meta%3Akeywords%22%3A%22Los%20Angeles%2C%20CA%22%7D&cd[OpenGraph]=%7B%22og%3Atype%22%3A%22website%22%2C%22og%3Aurl%22%3A%22https%3A%2F%2Fdowntownla.com%2F%22%2C%22og%3Asite_name%22%3A%22DowntownLA.com%22%2C%22og%3Aimage%22%3A%22https%3A%2F%2Fimg.ctykit.com%2Fcdn%2Fca-dtla%2Fimages%2Fhomesocial1200x600.jpg%22%2C%22og%3Aimage%3Awidth%22%3A%221200%22%2C%22og%3Aimage%3Aheight%22%3A%22600%22%2C%22og%3Atitle%22%3A%22DowntownLA.com%22%2C%22og%3Adescription%22%3A%22DowntownLA.com%20is%20proudly%20brought%20to%20you%20by%20the%20Downtown%20Center%20BID%2C%20a%20coalition%20of%20property%20owners%20committed%20to%20enhancing%20the%20quality%20of%20life%20in%20the%20Downtown%20Center.%22%7D&cd[Schema.org]=%5B%5D&cd[JSON-LD]=%5B%5D&sw=800&sh=600&v=2.9.83&r=stable&ec=1&o=30&fbp=fb.1.1663790213482.710675578&it=1663790213315&coo=false&es=automatic&tm=3&rqm=GET
h2
1306.8059999496
1319.6860000025
478
44
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
329.877
8.118
465.091
8.391
476.859
26.645
503.516
5.444
516.779
12.297
541.953
5.533
547.586
7.347
555.179
14.902
575.343
11.79
599.811
17.113
623.317
12.688
692.201
36.851
729.087
41.894
784.635
19.36
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Downtownla.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Downtownla.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Downtownla.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Downtownla.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 216 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Downtownla.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
/*! * Font Awesome Pro 6.2.0 by @fontawesome - https://fontawesome.com * License - https://fontawe...
165673
165337
https://ctycms.com/ca-dtla/css/cty_css_v21.min.css
26206
25518
/*! * Font Awesome Pro 6.2.0 by @fontawesome - https://fontawesome.com * License - https://fontawe...
18407
18407
https://downtownla.com/_templates/_styles.css?v=12f
13828
11802
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 200 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://downtownla.com/
195.867
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Downtownla.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://downtownla.com/
190
https://downtownla.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Downtownla.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
11330
https://connect.facebook.net/en_US/fbevents.js
45
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 1,183 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://ka-p.fontawesome.com/releases/v6.2.0/css/pro.min.css?token=1872c177cb
173956
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/home-things-shop-2022.jpg
151187
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
87077
https://use.typekit.net/af/cfc06a/00000000000000007735bbef/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i4&v=3
78218
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/bottega-louie-2.jpg
76618
https://use.typekit.net/af/5c4f69/00000000000000007735bbfb/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
72006
https://use.typekit.net/af/bdd682/00000000000000007735bbe9/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
71954
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/home-things-dining-2022.jpg
59649
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
55935
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
54348
Avoids an excessive DOM size — 575 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
575
Maximum DOM Depth
18
Maximum Child Elements
11
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Downtownla.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://downtownla.com/
119.822
3.154
1.136
Unattributable
54.028
3.892
0.185
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
135.205
Style & Layout
86.137
Other
69.633
Rendering
15.035
Parse HTML & CSS
12.084
Script Parsing & Compilation
6.54
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 35 requests • 1,183 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
35
1211437
Font
9
427350
Image
7
291346
Script
8
255157
Other
5
188356
Stylesheet
4
41693
Document
1
7535
Media
1
0
Third-party
32
1189811
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
312350
0
308093
0
116139
0
54348
0
21064
0
4275
0
685
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0004788305168841
0.00028818001752031
0.00023276201733649
0.00020360520094563
0.00012748817966903
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of downtownla.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 460 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Downtownla.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://ctycms.com/ca-dtla/css/cty_css_v21.min.css
26206
270
https://downtownla.com/_templates/_styles.css?v=12f
13828
80
https://use.typekit.net/ezz3lth.css
1323
230
Reduce unused JavaScript — Potential savings of 130 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
87077
69486
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
55935
42176
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
54348
21484
Serve static assets with an efficient cache policy — 6 resources found
Downtownla.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
1200000
87077
https://connect.facebook.net/en_US/fbevents.js
1200000
28106
https://www.google-analytics.com/analytics.js
7200000
20451
https://jscloud.net/x/5147/inlinks.js
14400000
673
https://acdn.adnxs.com/dmp/up/pixie.js
86402000
3928
https://p.typekit.net/p.css?s=1&k=ezz3lth&ht=tk&f=10879.10881.10884.10887.15586.39182.39184.39187&a=519809&app=typekit&e=css
604800000
336
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of downtownla.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Downtownla.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that downtownla.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
5.1.3
jQuery
3.6.0
core-js
core-js-pure@3.0.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://downtownla.com/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_CONNECTION_FAILED
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for downtownla.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of downtownla.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
56

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of downtownla.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of downtownla.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 84
Performance 76
Accessibility 100
Best Practices 83
SEO 100
PWA 60
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://downtownla.com/
Updated: 21st September, 2022

1.56 seconds
First Contentful Paint (FCP)
84%
11%
5%

0.01 seconds
First Input Delay (FID)
93%
5%
2%

Simulate loading on mobile
76

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for downtownla.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.016
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 120 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://downtownla.com/
http/1.1
0
64.431999999215
252
0
301
text/html
https://downtownla.com/
h2
64.821000007214
163.45400000864
7535
31362
200
text/html
Document
https://ctycms.com/ca-dtla/css/cty_css_v21.min.css
h2
179.83800001093
252.50400000368
26048
173289
200
text/css
Stylesheet
https://downtownla.com/_templates/_styles.css?v=12f
h2
180.11200000183
215.04000001005
13828
80565
200
text/css
Stylesheet
https://use.typekit.net/ezz3lth.css
h2
180.2949999983
205.541000003
1323
6144
200
text/css
Stylesheet
https://kit.fontawesome.com/1872c177cb.js
h2
255.90600000578
296.01200000616
4639
11075
200
text/javascript
Script
https://ctycms.com/ca-dtla/footer-logo-2.svg
h2
267.06399999966
341.92700000131
2588
6807
200
image/svg+xml
Image
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
h2
236.26499999955
358.63600000448
55935
174019
200
application/javascript
Script
https://jscloud.net/x/5147/inlinks.js
h2
267.18200001051
315.28800001252
671
0
200
application/javascript
Script
https://p.typekit.net/p.css?s=1&k=ezz3lth&ht=tk&f=10879.10881.10884.10887.15586.39182.39184.39187&a=519809&app=typekit&e=css
h2
208.05300000939
234.87600000226
317
5
200
text/css
Stylesheet
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
h2
267.61700000498
311.28400001035
54427
168614
200
application/javascript
Script
https://acdn.adnxs.com/dmp/up/pixie.js
http/1.1
268.06800000486
290.71300000942
3928
9139
200
application/javascript
Script
https://use.typekit.net/af/5c4f69/00000000000000007735bbfb/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
h2
276.39300000737
308.27300000237
72006
71688
200
application/font-woff2
Font
https://use.typekit.net/af/cfc06a/00000000000000007735bbef/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i4&v=3
h2
281.80700000667
313.0630000087
78218
77900
200
application/font-woff2
Font
https://use.typekit.net/af/309dfe/000000000000000000010091/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
h2
306.91800000204
334.94900001097
43394
43076
200
application/font-woff2
Font
https://use.typekit.net/af/bdd682/00000000000000007735bbe9/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
h2
307.20700000529
338.22099999816
71954
71636
200
application/font-woff2
Font
https://use.typekit.net/af/0c71d1/000000000000000000010097/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n8&v=3
h2
307.55500000669
337.51000001212
40862
40544
200
application/font-woff2
Font
https://img.ctykit.com/cdn/ca-dtla/docs/dcbid-looping-video-final-1080.mov
350.39900000265
1106.3880000002
0
0
-1
Media
https://ib.adnxs.com/pixie?e=PageView&pi=7a67b1cc-7f17-4ff1-a0e7-0f4075b2113b&it=1663790228489&v=0.0.20&u=https%3A%2F%2Fdowntownla.com%2F&st=1663790228488&et=1663790228489&if=0
http/1.1
438.35900000704
639.33000000543
347
42
200
image/gif
Image
https://www.google-analytics.com/analytics.js
h2
491.46400000609
499.56400001247
20451
49672
200
text/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
h2
495.63400000625
521.08400000725
28089
103160
200
application/x-javascript
Script
https://ka-p.fontawesome.com/releases/v6.2.0/css/pro.min.css?token=1872c177cb
h2
500.17800000205
605.78100000566
173956
807028
200
text/css
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/css/pro-v5-font-face.min.css?token=1872c177cb
h2
500.37700000394
535.62000000966
12839
85987
200
text/css
Fetch
https://www.google-analytics.com/j/collect?v=1&_v=j97&a=1934181822&t=pageview&_s=1&dl=https%3A%2F%2Fdowntownla.com%2F&ul=en-us&de=UTF-8&dt=Downtown%20LA&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAAABAAAAAC~&jid=2095352745&gjid=1332590465&cid=2102248887.1663790229&tid=UA-69671207-1&_gid=1362767827.1663790229&_r=1&gtm=2wg9j052H452&z=705998959
h2
539.14700000314
550.78100001265
613
2
200
text/plain
XHR
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/home-things-dining-2022.jpg
h2
543.6469999986
580.11999999871
59649
59074
200
image/webp
Image
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
h2
570.79100000556
624.86400001217
87094
299390
200
application/x-javascript
Script
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j97&tid=UA-69671207-1&cid=2102248887.1663790229&jid=2095352745&gjid=1332590465&_gid=1362767827.1663790229&_u=YEBAAAAAAAAAAC~&z=1476539350
h2
574.40199999837
585.31700000458
685
1
200
text/plain
XHR
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-brands-400-f6b769.woff2
h2
742.48500000976
770.20500000799
18875
18440
200
font/woff2
Font
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-brands-400-9b80fe.woff2
h2
742.81500000507
765.34900000843
45874
45440
200
font/woff2
Font
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-solid-900-51b08f.woff2
h2
743.0510000122
770.75100000366
27675
27240
200
font/woff2
Font
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-light-300-d5bbe9.woff2
h2
743.28600001172
771.7440000124
32531
32096
200
font/woff2
Font
https://www.facebook.com/tr/?id=275012842862574&ev=PageView&dl=https%3A%2F%2Fdowntownla.com%2F&rl=&if=false&ts=1663790228865&sw=360&sh=640&v=2.9.83&r=stable&ec=0&o=30&fbp=fb.1.1663790228862.510376112&it=1663790228623&coo=false&rqm=GET
h2
813.10600000143
837.5789999991
478
44
200
image/gif
Image
https://www.facebook.com/tr/?id=275012842862574&ev=Microdata&dl=https%3A%2F%2Fdowntownla.com%2F&rl=&if=false&ts=1663790229372&cd[DataLayer]=%5B%5D&cd[Meta]=%7B%22title%22%3A%22Downtown%20LA%22%2C%22meta%3Adescription%22%3A%22DowntownLA.com%20is%20proudly%20brought%20to%20you%20by%20the%20Downtown%20Center%20BID%2C%20a%20coalition%20of%20property%20owners%20committed%20to%20enhancing%20the%20quality%20of%20life%20in%20the%20Downtown%20Center.%22%2C%22meta%3Akeywords%22%3A%22Los%20Angeles%2C%20CA%22%7D&cd[OpenGraph]=%7B%22og%3Atype%22%3A%22website%22%2C%22og%3Aurl%22%3A%22https%3A%2F%2Fdowntownla.com%2F%22%2C%22og%3Asite_name%22%3A%22DowntownLA.com%22%2C%22og%3Aimage%22%3A%22https%3A%2F%2Fimg.ctykit.com%2Fcdn%2Fca-dtla%2Fimages%2Fhomesocial1200x600.jpg%22%2C%22og%3Aimage%3Awidth%22%3A%221200%22%2C%22og%3Aimage%3Aheight%22%3A%22600%22%2C%22og%3Atitle%22%3A%22DowntownLA.com%22%2C%22og%3Adescription%22%3A%22DowntownLA.com%20is%20proudly%20brought%20to%20you%20by%20the%20Downtown%20Center%20BID%2C%20a%20coalition%20of%20property%20owners%20committed%20to%20enhancing%20the%20quality%20of%20life%20in%20the%20Downtown%20Center.%22%7D&cd[Schema.org]=%5B%5D&cd[JSON-LD]=%5B%5D&sw=360&sh=640&v=2.9.83&r=stable&ec=1&o=30&fbp=fb.1.1663790228862.510376112&it=1663790228623&coo=false&es=automatic&tm=3&rqm=GET
h2
1320.2190000011
1332.5520000071
478
44
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
173.104
12.475
256.062
9.107
268.816
17.014
287.749
5.296
293.089
47.546
340.65
11.595
357.697
6.729
366.463
6.76
373.798
9.241
385.892
7.901
403.912
27.379
432.402
7.166
439.795
29.135
468.992
10.738
481.474
15.662
497.477
6.807
511.224
28.436
551.783
20.04
609.559
6.848
620.076
61.734
681.902
83.369
781.175
5.575
787.086
26.632
1312.829
6.211
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Downtownla.com should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 3 KiB
Time to Interactive can be slowed down by resources on the page. Downtownla.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://ctycms.com/ca-dtla/footer-logo-2.svg
2588
2588
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Downtownla.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Downtownla.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://downtownla.com/
99.613
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Downtownla.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://downtownla.com/
630
https://downtownla.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Downtownla.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
11332
https://connect.facebook.net/en_US/fbevents.js
45
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 964 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://ka-p.fontawesome.com/releases/v6.2.0/css/pro.min.css?token=1872c177cb
173956
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
87094
https://use.typekit.net/af/cfc06a/00000000000000007735bbef/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=i4&v=3
78218
https://use.typekit.net/af/5c4f69/00000000000000007735bbfb/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n4&v=3
72006
https://use.typekit.net/af/bdd682/00000000000000007735bbe9/30/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
71954
https://img.ctykit.com/cdn/ca-dtla/images/tr:w-1200/home-things-dining-2022.jpg
59649
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
55935
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
54427
https://ka-p.fontawesome.com/releases/v6.2.0/webfonts/pro-fa-brands-400-9b80fe.woff2
45874
https://use.typekit.net/af/309dfe/000000000000000000010091/27/l?primer=7cdcb44be4a7db8877ffa5c0007b8dd865b3bbc383831fe2ea177f62257a9191&fvd=n7&v=3
43394
Avoids an excessive DOM size — 575 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
575
Maximum DOM Depth
18
Maximum Child Elements
11
Avoid chaining critical requests — 13 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Downtownla.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://downtownla.com/
856.984
15.632
6.912
Unattributable
464.504
18.932
1.084
https://kit.fontawesome.com/1872c177cb.js
264.076
259.42
0.7
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
136.052
105.836
5.444
https://www.google-analytics.com/analytics.js
133.468
117.244
1.784
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
131.372
108.088
16.488
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
130.84
111.016
5.016
https://connect.facebook.net/en_US/fbevents.js
80.548
75.52
3.42
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 33 requests • 964 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
33
987559
Font
9
431389
Script
8
255234
Other
5
188345
Image
5
63540
Stylesheet
4
41516
Document
1
7535
Media
1
0
Third-party
30
965944
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.01396299235026
0.0015988159179687
1.5997992621528E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://kit.fontawesome.com/1872c177cb.js
2090
247
https://downtownla.com/
1390
167
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
3990
117
https://www.google-analytics.com/analytics.js
4726
114
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
6456
107
https://downtownla.com/
1194
95
https://connect.facebook.net/en_US/fbevents.js
4876
80
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
3433
63
https://downtownla.com/
1335
55
https://downtownla.com/
1110
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of downtownla.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 2.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 6.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 200 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 4.0 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 4.0 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 217 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Downtownla.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
/*! * Font Awesome Pro 6.2.0 by @fontawesome - https://fontawesome.com * License - https://fontawe...
165673
165376
https://ctycms.com/ca-dtla/css/cty_css_v21.min.css
26048
25422
/*! * Font Awesome Pro 6.2.0 by @fontawesome - https://fontawesome.com * License - https://fontawe...
18407
18407
https://downtownla.com/_templates/_styles.css?v=12f
13828
12495
Serve static assets with an efficient cache policy — 6 resources found
Downtownla.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
1200000
87094
https://connect.facebook.net/en_US/fbevents.js
1200000
28089
https://www.google-analytics.com/analytics.js
7200000
20451
https://jscloud.net/x/5147/inlinks.js
14400000
671
https://acdn.adnxs.com/dmp/up/pixie.js
86402000
3928
https://p.typekit.net/p.css?s=1&k=ezz3lth&ht=tk&f=10879.10881.10884.10887.15586.39182.39184.39187&a=519809&app=typekit&e=css
604800000
317
Minimize main-thread work — 2.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
839.836
Style & Layout
678.08
Other
589.232
Parse HTML & CSS
85.668
Rendering
58.056
Script Parsing & Compilation
42.812

Other

Eliminate render-blocking resources — Potential savings of 1,530 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Downtownla.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://ctycms.com/ca-dtla/css/cty_css_v21.min.css
26048
1080
https://downtownla.com/_templates/_styles.css?v=12f
13828
300
https://use.typekit.net/ezz3lth.css
1323
780
Reduce unused JavaScript — Potential savings of 130 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://connect.facebook.net/signals/config/275012842862574?v=2.9.83&r=stable
87094
69499
https://ctycms.com/ca-dtla/js/cty_js_v7.min.js
55935
42176
https://www.googletagmanager.com/gtm.js?id=GTM-52H452
54427
21514
Reduce the impact of third-party code — Third-party code blocked the main thread for 310 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
316389
191.08
21064
58.268
116139
53.348
54427
6.236
308074
0
4275
0
685
0
First Contentful Paint (3G) — 5220 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of downtownla.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Downtownla.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that downtownla.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
5.1.3
jQuery
3.6.0
core-js
core-js-pure@3.0.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://downtownla.com/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_CONNECTION_FAILED
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for downtownla.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of downtownla.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
60

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of downtownla.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of downtownla.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 75.2.44.162
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Amazon.com, Inc.
Registration

Domain Registrant

Private Registration: No
Name: Downtown Center Business Improve Dist Mgm
Organization: Downtown Center Business Improve Dist Mgm
Country: US
City: LOS ANGELES
State: CA
Post Code: 90017-2915
Email: citsadmin@crimsonit.com
Phone: +1.2136242146
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Network Solutions, LLC 162.159.133.53
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: downtownla.com
Issued By: Amazon
Valid From: 27th June, 2022
Valid To: 26th July, 2023
Subject: CN = downtownla.com
Hash: 97160e11
Issuer: CN = Amazon
OU = Server CA 1B
O = Amazon
S = US
Version: 2
Serial Number: 17661209464749121826584039206305517880
Serial Number (Hex): 0D496CDAF87682353A2D6D857205D138
Valid From: 27th June, 2024
Valid To: 26th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:59:A4:66:06:52:A0:7B:95:92:3C:A3:94:07:27:96:74:5B:F9:3D:D0
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sca1b.amazontrust.com/sca1b-1.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.sca1b.amazontrust.com
CA Issuers - URI:http://crt.sca1b.amazontrust.com/sca1b.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jun 27 05:43:10.910 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C5:7D:6B:3D:5E:79:DA:20:79:BC:58:
A2:13:E4:C3:14:80:1E:13:8A:84:43:5F:A1:55:2F:4F:
02:AE:06:75:42:02:21:00:A1:B4:A4:6D:36:C0:51:39:
DA:E2:82:7A:53:8C:83:3C:A6:6D:55:98:6B:76:0E:0D:
91:5F:30:E9:5C:B5:6E:BB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Jun 27 05:43:10.722 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:4D:CF:56:60:FA:DE:11:97:70:82:63:EB:
10:E9:5F:80:5A:3C:C2:B3:9F:AD:47:44:E2:73:EF:61:
37:E2:69:5F:02:20:7F:C3:B6:C1:61:E1:BB:A0:CF:5B:
8F:DE:3D:51:E2:83:B0:8C:DB:3B:32:A4:32:BC:55:2B:
42:AC:4B:1D:FE:06
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Jun 27 05:43:10.795 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:47:01:D9:E6:DB:12:60:7F:19:50:C1:2B:
EF:A3:58:07:09:66:DD:66:12:FC:90:55:B1:2A:7E:C2:
CB:06:79:2A:02:21:00:9B:36:41:84:F8:6F:09:1A:1F:
1C:99:E5:91:E0:6A:81:2B:93:21:82:5C:61:1E:B8:ED:
89:80:D6:2A:80:04:17
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.downtownla.com
DNS:downtownla.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
downtownla.com. 75.2.44.162 IN 3599

NS Records

Host Nameserver Class TTL
downtownla.com. ns69.worldnic.com. IN 7199
downtownla.com. ns70.worldnic.com. IN 7199

MX Records

Priority Host Server Class TTL
20 downtownla.com. mx2-us1.ppe-hosted.com. IN 3599
10 downtownla.com. mx1-us1.ppe-hosted.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
downtownla.com. ns69.worldnic.com. namehost.worldnic.com. 7199

TXT Records

Host Value Class TTL
downtownla.com. v=spf1 IN 3599
downtownla.com. MS=ms27286352 IN 3599
downtownla.com. ppe-effe9401ba9867275f91 IN 3599
downtownla.com. google-site-verification=6VeRmokpyThaFkg0V_0Ize5r6afIEE4bchJ_KKYkHRE IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 23rd February, 2023
Content-Type: text/html; charset=UTF-8
Server: Apache/2.4.54 ()
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate
Connection: keep-alive
X-Powered-By: PHP/7.2.34
Pragma: no-cache
Set-Cookie: *
X-Frame-Options: DENY
Content-Security-Policy: frame-ancestors 'self' https://citylightcloud.com https://geocentric.com explore.vistity.com vistity.com www.vistity.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Type-Options: nosniff
Vary: User-Agent

Whois Lookup

Created: 11th July, 1996
Changed: 4th February, 2022
Expires: 10th July, 2031
Registrar: Network Solutions, LLC
Status: clientTransferProhibited
Nameservers: ns69.worldnic.com
ns70.worldnic.com
Owner Name: Downtown Center Business Improve Dist Mgm
Owner Organization: Downtown Center Business Improve Dist Mgm
Owner Street: 626 WILSHIRE BLVD STE 200
Owner Post Code: 90017-2915
Owner City: LOS ANGELES
Owner State: CA
Owner Country: US
Owner Phone: +1.2136242146
Owner Email: citsadmin@crimsonit.com
Admin Name: Flores, Ernie
Admin Organization: Downtown Center Business Improvement District Management Corp.
Admin Street: 626 WILSHIRE BLVD STE 200
Admin Post Code: 90017-2915
Admin City: LOS ANGELES
Admin State: CA
Admin Country: US
Admin Phone: +1.2136242146
Admin Email: citsadmin@crimsonit.com
Tech Street: Linkline Communications
Tech Post Code: 91752
Tech City: Mira Loma
Tech State: CA
Tech Country: US
Tech Phone: +1.9097275051
Tech Email: hostmaster@LINKLINE.COM
Full Whois: Domain Name: DOWNTOWNLA.COM
Registry Domain ID: 4767378_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://networksolutions.com
Updated Date: 2022-02-04T19:27:39Z
Creation Date: 1996-07-11T04:00:00Z
Registrar Registration Expiration Date: 2031-07-10T04:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Downtown Center Business Improve Dist Mgm
Registrant Organization: Downtown Center Business Improve Dist Mgm
Registrant Street: 626 WILSHIRE BLVD STE 200
Registrant City: LOS ANGELES
Registrant State/Province: CA
Registrant Postal Code: 90017-2915
Registrant Country: US
Registrant Phone: +1.2136242146
Registrant Phone Ext:
Registrant Fax: +1.2136240858
Registrant Fax Ext:
Registrant Email: citsadmin@crimsonit.com
Registry Admin ID:
Admin Name: Flores, Ernie
Admin Organization: Downtown Center Business Improvement District Management Corp.
Admin Street: 626 WILSHIRE BLVD STE 200
Admin City: LOS ANGELES
Admin State/Province: CA
Admin Postal Code: 90017-2915
Admin Country: US
Admin Phone: +1.2136242146
Admin Phone Ext:
Admin Fax: +1.2136240858
Admin Fax Ext:
Admin Email: citsadmin@crimsonit.com
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street: Linkline Communications
Tech City: Mira Loma
Tech State/Province: CA
Tech Postal Code: 91752
Tech Country: US
Tech Phone: +1.9097275051
Tech Phone Ext:
Tech Fax: +1.9999999999
Tech Fax Ext:
Tech Email: hostmaster@LINKLINE.COM
Name Server: NS69.WORLDNIC.COM
Name Server: NS70.WORLDNIC.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: domain.operations@web.com
Registrar Abuse Contact Phone: +1.8777228662
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-02-23T18:39:36Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en


The data in Networksolutions.com's WHOIS database is provided to you by
Networksolutions.com for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. Networksolutions.com makes this information available "as is," and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that,
under no circumstances will you use this data to: (1) allow, enable,
or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to Networksolutions.com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of Networksolutions.com.
Networksolutions.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
ns69.worldnic.com 162.159.26.185
ns70.worldnic.com 162.159.27.127
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,786 USD 1/5
0/5
0/5
0/5
$2,477 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$884 USD 1/5