Follow recommendations of this health report to keep your site healthy
Examined at : 2022-06-15 02:41:46
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
DTLA | 15 | 1.616 % | No |
Downtown | 11 | 1.185 % | No |
District | 9 | 0.97 % | No |
LA | 8 | 0.862 % | No |
Los | 6 | 0.647 % | No |
– | 6 | 0.647 % | No |
Angeles | 6 | 0.647 % | No |
Historic | 5 | 0.539 % | No |
Gusto | 5 | 0.539 % | No |
Green | 5 | 0.539 % | No |
long | 4 | 0.431 % | No |
Exhibit | 3 | 0.323 % | No |
Core | 3 | 0.323 % | No |
Muralist | 3 | 0.323 % | No |
Coming | 3 | 0.323 % | No |
Vegan | 3 | 0.323 % | No |
Awards | 3 | 0.323 % | No |
Weekly | 3 | 0.323 % | No |
news | 3 | 0.323 % | No |
Get2DTLA | 3 | 0.323 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Los Angeles | 6 | 0.647 % | No |
Gusto Green | 5 | 0.539 % | No |
of the | 4 | 0.431 % | No |
to the | 4 | 0.431 % | No |
Right Climate | 3 | 0.323 % | No |
the Right | 3 | 0.323 % | No |
Just the | 3 | 0.323 % | No |
up to | 3 | 0.323 % | No |
Downtown LA | 3 | 0.323 % | No |
Climate at | 3 | 0.323 % | No |
Coming to | 3 | 0.323 % | No |
Spirits Awards | 3 | 0.323 % | No |
LA Spirits | 3 | 0.323 % | No |
Grand Central | 3 | 0.323 % | No |
Historic Core | 3 | 0.323 % | No |
DTLA Vegan | 3 | 0.323 % | No |
in the | 3 | 0.323 % | No |
at Gusto | 3 | 0.323 % | No |
of Downtown | 3 | 0.323 % | No |
Downtown Los | 3 | 0.323 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Climate at Gusto | 3 | 0.323 % | No |
LA Spirits Awards | 3 | 0.323 % | No |
Just the Right | 3 | 0.323 % | No |
Right Climate at | 3 | 0.323 % | No |
at Gusto Green | 3 | 0.323 % | No |
Downtown Los Angeles | 3 | 0.323 % | No |
the Right Climate | 3 | 0.323 % | No |
Coming to City | 2 | 0.216 % | No |
Vegan Weekend Returns… | 2 | 0.216 % | No |
up to receive | 2 | 0.216 % | No |
Sign up to | 2 | 0.216 % | No |
Gusto Green 20220612 | 2 | 0.216 % | No |
Exhibit Opens at | 2 | 0.216 % | No |
Grand Central Market | 2 | 0.216 % | No |
a Wholesome Vibe | 2 | 0.216 % | No |
It’s a Wholesome | 2 | 0.216 % | No |
and It’s a | 2 | 0.216 % | No |
Returns… and It’s | 2 | 0.216 % | No |
Weekend Returns… and | 2 | 0.216 % | No |
DTLA Vegan Weekend | 2 | 0.216 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
the Right Climate at | 3 | 0.323 % | No |
Just the Right Climate | 3 | 0.323 % | No |
Climate at Gusto Green | 3 | 0.323 % | No |
Right Climate at Gusto | 3 | 0.323 % | No |
After a long cold | 2 | 0.216 % | No |
20220612 After a long | 2 | 0.216 % | No |
up to receive our | 2 | 0.216 % | No |
Sign up to receive | 2 | 0.216 % | No |
Green 20220612 After a | 2 | 0.216 % | No |
at Gusto Green 20220612 | 2 | 0.216 % | No |
Awards Coming to City | 2 | 0.216 % | No |
Spirits Awards Coming to | 2 | 0.216 % | No |
LA Spirits Awards Coming | 2 | 0.216 % | No |
Exhibit Opens at US | 2 | 0.216 % | No |
Opens at US Bank | 2 | 0.216 % | No |
High Muralist Exhibit Opens | 2 | 0.216 % | No |
long cold covid winter | 2 | 0.216 % | No |
at US Bank Building | 2 | 0.216 % | No |
2nd Annual DTLA Vegan | 2 | 0.216 % | No |
Annual DTLA Vegan Weekend | 2 | 0.216 % | No |
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" />
directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a>
if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
SL | Host | Class | TTL | Type | PRI | Target | IP |
1 | dtlaweekly.com | IN | 2069 | A | 192.124.249.167 | ||
2 | dtlaweekly.com | IN | 2070 | NS | ns26.domaincontrol.com | ||
3 | dtlaweekly.com | IN | 2070 | NS | ns25.domaincontrol.com | ||
4 | dtlaweekly.com | IN | 2070 | MX | 1 | aspmx.l.google.com | |
5 | dtlaweekly.com | IN | 2070 | MX | 5 | alt2.aspmx.l.google.com | |
6 | dtlaweekly.com | IN | 2070 | MX | 10 | alt4.aspmx.l.google.com | |
7 | dtlaweekly.com | IN | 2070 | MX | 5 | alt1.aspmx.l.google.com | |
8 | dtlaweekly.com | IN | 2070 | MX | 10 | alt3.aspmx.l.google.com |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://dtlaweekly.com/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 568 |
request size | 289 | filetime | -1 |
ssl verify result | 0 | redirect count | 0 |
total time | 0.993451 | namelookup time | 0.000719 |
connect time | 0.044524 | pretransfer time | 0.104294 |
size upload | 0 | size download | 169188 |
speed download | 170380 | speed upload | 0 |
download content length | -1 | upload content length | -1 |
starttransfer time | 0.681527 | redirect time | 0 |
redirect url | primary ip | 192.124.249.167 | |
certinfo | primary port | 443 | |
local ip | 162.0.209.211 | local port | 34644 |
http version | 3 | protocol | 2 |
ssl verifyresult | 0 | scheme | HTTPS |
appconnect time us | 103939 | connect time us | 44524 |
namelookup time us | 719 | pretransfer time us | 104294 |
redirect time us | 0 | starttransfer time us | 681527 |
total time us | 993451 |
196 requests • 15,837 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 3,190 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Potential savings of 30 KiB
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
25 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 3,320 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
11460 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More
2,840 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
7.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Potential savings of 15 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Potential savings of 290 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 74 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 15,837 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
13.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
36 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
742 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More
250 requests • 15,993 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Potential savings of 217 KiB
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
24 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 470 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
270 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
2.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Potential savings of 435 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 131 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 15,993 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
36 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
764 elements
A large DOM will increase memory usage, cause longer Learn More
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More