Powered by https://sitehealthcheck.net ()
health report : https://uniliv.in/
examined at : 24-04-22 05:51:32
follow recommendations of this health report to keep your site healthy
Powered by https://sitehealthcheck.net ()
examined at : 24-04-22 05:51:32
follow recommendations of this health report to keep your site healthy
PG in Delhi University | PG with food near DU | Uniliv
Your page title does not exceed 60 characters. It's fine.
Find PG in Delhi University: If you are looking for a PG with food near DU, Then we can provide you best PG in DU for boys & girls.
Your meta description does not exceed 150 characters. It's fine.
Your site do not have any meta keyword.
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Girls | 22 | 1.91 % | No |
| pg | 20 | 1.736 % | No |
| Uniliv | 20 | 1.736 % | No |
| PG | 19 | 1.649 % | No |
| college | 17 | 1.476 % | No |
| College | 11 | 0.955 % | No |
| Boys | 11 | 0.955 % | No |
| Delhi | 10 | 0.868 % | No |
| Saket | 8 | 0.694 % | No |
| home | 8 | 0.694 % | Yes |
| Home | 7 | 0.608 % | Yes |
| HOME | 7 | 0.608 % | Yes |
| place | 6 | 0.521 % | No |
| Conest | 6 | 0.521 % | No |
| Metro | 6 | 0.521 % | No |
| close | 5 | 0.434 % | No |
| Station | 5 | 0.434 % | No |
| Maple | 5 | 0.434 % | No |
| food | 4 | 0.347 % | No |
| Shaheed | 4 | 0.347 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Girls PG | 18 | 1.563 % | No |
| PG near | 18 | 1.563 % | No |
| college Girls | 12 | 1.042 % | No |
| pg near | 11 | 0.955 % | No |
| Boys pg | 9 | 0.781 % | No |
| It is | 6 | 0.521 % | No |
| is near | 5 | 0.434 % | No |
| Metro Station | 5 | 0.434 % | No |
| close to | 5 | 0.434 % | No |
| is a | 4 | 0.347 % | No |
| all the | 4 | 0.347 % | No |
| of the | 4 | 0.347 % | No |
| away from | 4 | 0.347 % | No |
| from home | 4 | 0.347 % | No |
| is the | 4 | 0.347 % | No |
| a safe | 4 | 0.347 % | No |
| Bhagat Singh | 3 | 0.26 % | No |
| College Girls | 3 | 0.26 % | No |
| Singh College | 3 | 0.26 % | No |
| College and | 3 | 0.26 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| Girls PG near | 18 | 1.563 % | No |
| college Girls PG | 10 | 0.868 % | No |
| Boys pg near | 9 | 0.781 % | No |
| away from home | 4 | 0.347 % | No |
| college Boys pg | 3 | 0.26 % | No |
| College Girls PG | 3 | 0.26 % | No |
| to build a | 3 | 0.26 % | No |
| Bhagat Singh College | 3 | 0.26 % | No |
| Shaheed Bhagat Singh | 3 | 0.26 % | No |
| of the word | 2 | 0.174 % | No |
| meaning of the | 2 | 0.174 % | No |
| to the literal | 2 | 0.174 % | No |
| Homes OAK HOME | 2 | 0.174 % | No |
| the word Saket | 2 | 0.174 % | No |
| literal meaning of | 2 | 0.174 % | No |
| the literal meaning | 2 | 0.174 % | No |
| is near Durga | 2 | 0.174 % | No |
| Our Homes OAK | 2 | 0.174 % | No |
| justice to the | 2 | 0.174 % | No |
| are all the | 2 | 0.174 % | No |
| Keyword | Occurrence | Density | Possible Spam |
|---|---|---|---|
| college Girls PG near | 10 | 0.868 % | No |
| Shaheed Bhagat Singh College | 3 | 0.26 % | No |
| College Girls PG near | 3 | 0.26 % | No |
| college Boys pg near | 3 | 0.26 % | No |
| Our Homes OAK HOME | 2 | 0.174 % | No |
| area does complete justice | 2 | 0.174 % | No |
| The area does complete | 2 | 0.174 % | No |
| be The area does | 2 | 0.174 % | No |
| to be The area | 2 | 0.174 % | No |
| place to be The | 2 | 0.174 % | No |
| the place to be | 2 | 0.174 % | No |
| is the place to | 2 | 0.174 % | No |
| What are all the | 2 | 0.174 % | No |
| does complete justice to | 2 | 0.174 % | No |
| Saket is the place | 2 | 0.174 % | No |
| Delhi Saket is the | 2 | 0.174 % | No |
| South Delhi Saket is | 2 | 0.174 % | No |
| in South Delhi Saket | 2 | 0.174 % | No |
| Bai Deshmukh Metro Station | 2 | 0.174 % | No |
| Durga Bai Deshmukh Metro | 2 | 0.174 % | No |
The most using keywords do not match with meta keywords.
Your site have sitemap
https://uniliv.in/sitemap_index.xml
1152
Text/HTML Ratio Test : 13%
Your site have robot.txt
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.
Some links of your site are not SEO friendly.
Site failed plain text email test.4plain text email found.
Page have doc type.
Your site have 4 images without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is disabled.
Your site have 48 inline css.
Your site have 17 internal css.
Site passed micro data schema test. 2 results found.
| SL | Host | Class | TTL | Type | PRI | Target | IP |
|---|---|---|---|---|---|---|---|
| 1 | uniliv.in | IN | 1800 | A | 89.117.157.13 | ||
| 2 | uniliv.in | IN | 86400 | NS | ns2.dns-parking.com | ||
| 3 | uniliv.in | IN | 86400 | NS | ns1.dns-parking.com | ||
| 4 | uniliv.in | IN | 14400 | MX | 10 | ALT4.ASPMX.L.GOOGLE.COM | |
| 5 | uniliv.in | IN | 14400 | MX | 5 | ALT1.ASPMX.L.GOOGLE.COM | |
| 6 | uniliv.in | IN | 14400 | MX | 1 | ASPMX.L.GOOGLE.COM | |
| 7 | uniliv.in | IN | 14400 | MX | 5 | ALT2.ASPMX.L.GOOGLE.COM | |
| 8 | uniliv.in | IN | 14400 | MX | 10 | ALT3.ASPMX.L.GOOGLE.COM | |
| 9 | uniliv.in | IN | 14400 | MX | 10 | mx2.hostinger.COM | |
| 10 | uniliv.in | IN | 14400 | MX | 5 | mx1.hostinger.COM | |
| 11 | uniliv.in | IN | 1800 | AAAA | 2a02:4780:11:1099::25f5:409e:2 |
Site failed IP canonicalization test.
Site passed URL canonicalization test.
<link rel="canonical" href="https://mywebsite.com/home" /><link rel="canonical" href="https://www.mywebsite.com/home" />
Aggregates all network requests and groups them by typeLearn More
Potential savings of 2,940 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 67 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
43 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,890 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,480 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
Potential savings of 3,065 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
630 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 882 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 187 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 6,353 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
10.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
79 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
1,055 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 8 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
380 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
Aggregates all network requests and groups them by typeLearn More
Potential savings of 830 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 67 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
43 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 270 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
170 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.7 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 125 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
750 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 1,049 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 188 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 6,352 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
79 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
1,067 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 8 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
6 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
380 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