Follow recommendations of this health report to keep your site healthy
Examined at : 2023-05-17 12:22:13
Score
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Add | 64 | 7.556 % | No |
cart | 34 | 4.014 % | No |
wishlist | 32 | 3.778 % | No |
Sale | 32 | 3.778 % | Yes |
View | 32 | 3.778 % | No |
Quick | 32 | 3.778 % | No |
Earrings | 31 | 3.66 % | No |
Stud | 19 | 2.243 % | No |
Bracelets | 17 | 2.007 % | No |
studs | 17 | 2.007 % | No |
₨1990 | 14 | 1.653 % | No |
Accessories | 10 | 1.181 % | No |
₨2450 | 9 | 1.063 % | No |
₨1590 | 8 | 0.945 % | No |
₨2990 | 7 | 0.826 % | No |
Jewelry | 6 | 0.708 % | No |
Bangles | 6 | 0.708 % | No |
Rings | 6 | 0.708 % | No |
Exclusive | 6 | 0.708 % | No |
Sunglasses | 6 | 0.708 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Add to | 64 | 7.556 % | No |
Sale Add | 32 | 3.778 % | No |
to wishlist | 32 | 3.778 % | No |
wishlist Quick | 32 | 3.778 % | No |
Quick View | 32 | 3.778 % | No |
to cart | 32 | 3.778 % | No |
cart Sale | 30 | 3.542 % | No |
Stud Earrings | 19 | 2.243 % | No |
View Stud | 17 | 2.007 % | No |
₨1590 Add | 8 | 0.945 % | No |
₨2450 ₨1990 | 8 | 0.945 % | No |
₨1990 Add | 8 | 0.945 % | No |
View Bracelets | 7 | 0.826 % | No |
₨3450 ₨2990 | 6 | 0.708 % | No |
₨2990 Add | 6 | 0.708 % | No |
studs ₨1990 | 5 | 0.59 % | No |
₨1990 ₨1590 | 5 | 0.59 % | No |
Earrings Jhumkis | 5 | 0.59 % | No |
Hair Accessories | 4 | 0.472 % | No |
Bangles and | 4 | 0.472 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Add to cart | 32 | 3.778 % | No |
Sale Add to | 32 | 3.778 % | No |
wishlist Quick View | 32 | 3.778 % | No |
to wishlist Quick | 32 | 3.778 % | No |
Add to wishlist | 32 | 3.778 % | No |
cart Sale Add | 30 | 3.542 % | No |
to cart Sale | 30 | 3.542 % | No |
Quick View Stud | 17 | 2.007 % | No |
View Stud Earrings | 17 | 2.007 % | No |
₨1590 Add to | 8 | 0.945 % | No |
₨1990 Add to | 8 | 0.945 % | No |
₨2450 ₨1990 Add | 8 | 0.945 % | No |
Quick View Bracelets | 7 | 0.826 % | No |
₨3450 ₨2990 Add | 6 | 0.708 % | No |
₨2990 Add to | 6 | 0.708 % | No |
studs ₨1990 ₨1590 | 5 | 0.59 % | No |
₨1990 ₨1590 Add | 5 | 0.59 % | No |
Earrings Mesmerizing floral | 4 | 0.472 % | No |
studs ₨3450 ₨2990 | 4 | 0.472 % | No |
₨990 ₨750 Add | 4 | 0.472 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Add to wishlist Quick | 32 | 3.778 % | No |
Sale Add to wishlist | 32 | 3.778 % | No |
to wishlist Quick View | 32 | 3.778 % | No |
Add to cart Sale | 30 | 3.542 % | No |
cart Sale Add to | 30 | 3.542 % | No |
to cart Sale Add | 30 | 3.542 % | No |
wishlist Quick View Stud | 17 | 2.007 % | No |
Quick View Stud Earrings | 17 | 2.007 % | No |
₨2450 ₨1990 Add to | 8 | 0.945 % | No |
₨1590 Add to cart | 8 | 0.945 % | No |
₨1990 Add to cart | 8 | 0.945 % | No |
wishlist Quick View Bracelets | 7 | 0.826 % | No |
₨3450 ₨2990 Add to | 6 | 0.708 % | No |
₨2990 Add to cart | 6 | 0.708 % | No |
studs ₨1990 ₨1590 Add | 5 | 0.59 % | No |
₨1990 ₨1590 Add to | 5 | 0.59 % | No |
studs ₨3450 ₨2990 Add | 4 | 0.472 % | No |
Stud Earrings Mesmerizing floral | 4 | 0.472 % | No |
₨750 Add to cart | 4 | 0.472 % | No |
Quick View Earrings Jhumkis | 4 | 0.472 % | No |
Severity: Notice
Message: Trying to access array offset on value of type null
Filename: site/report.php
Line Number: 936
Severity: Notice
Message: Trying to access array offset on value of type null
Filename: site/report.php
Line Number: 946
Severity: Notice
Message: Trying to access array offset on value of type null
Filename: site/report.php
Line Number: 956
Severity: Notice
Message: Trying to access array offset on value of type null
Filename: site/report.php
Line Number: 966
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 | dazzle.com.pk | IN | 14396 | A | 192.185.16.124 | ||
2 | dazzle.com.pk | IN | 21600 | NS | ns8113.hostgator.com | ||
3 | dazzle.com.pk | IN | 21600 | NS | ns8114.hostgator.com | ||
4 | www.dazzle.com.pk | IN | 14396 | CNAME | dazzle.com.pk | ||
5 | dazzle.com.pk | IN | 14400 | MX | 0 | mail.dazzle.com.pk |
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
url | https://dazzle.com.pk/ | content type | text/html; charset=UTF-8 |
http code | 200 | header size | 1279 |
request size | 268 | filetime | -1 |
ssl verify result | 20 | redirect count | 1 |
total time | 1.367401 | namelookup time | 0.026734 |
connect time | 0.041036 | pretransfer time | 0.068449 |
size upload | 0 | size download | 296341 |
speed download | 216718 | speed upload | 0 |
download content length | -1 | upload content length | 0 |
starttransfer time | 1.048754 | redirect time | 0.511187 |
redirect url | primary ip | 192.185.16.124 | |
certinfo | primary port | 443 | |
local ip | 151.106.99.4 | local port | 54734 |
http version | 3 | protocol | 2 |
ssl verifyresult | 0 | scheme | HTTPS |
appconnect time us | 68237 | connect time us | 41036 |
namelookup time us | 26734 | pretransfer time us | 68449 |
redirect time us | 511187 | starttransfer time us | 1048754 |
total time us | 1367401 |
117 requests • 8,525 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 1,820 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
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
31 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 1,460 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
1,950 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
3.1 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 3,248 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 89 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 8,525 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
12.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
43 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
2,324 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 4 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
116 requests • 7,371 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn More
Potential savings of 430 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
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
31 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 20 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
50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.3 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 2,958 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 86 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 7,371 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
43 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
2,324 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Potential savings of 4 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