Your Website Score is

Similar Ranking

47
WEBSITE VALUE CALCULATOR AND WEB INFORMATION
websiteoutlook.com
47
INTERNET SPEED TEST | FAST.COM
fast.com
47
ERROR PAGE | EBAY
ebay.ie
47
THE WORK MANAGEMENT PLATFORM | PIPEFY
pipefy.com
47
MIS MARCADORES: RESULTADOS DE FÚTBOL EN DIRECTO, FÚTBOL EN VIVO
mismarcadores.com
47
企查查-企业工商信息查询系统_查企业_查老板_查关系就上企查查!
qichacha.com
47
URLAUB: BIS 40% RABATT BEIM MARKTFÜHRER | AB-IN-DEN-URLAUB.DE
ab-in-den-urlaub.de

Latest Sites

21
GOLIKE
tiktok.golike.one
41
ACUITY FUNDING
acuityfunding.com
1
-
sharenow126.com
6
MASUK
gm066.com
34
恭喜，站点创建成功！
51278.cc
1
-
m.fun8899jk.com
3
JOBIFY
jobify2u.com

Top Technologies

Nginx
Web Servers
PHP
Programming Languages
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
jQuery
JavaScript Frameworks
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

47 licindia.in Last Updated: 1 year

Success 63% of passed verification steps
Warning 7% of total warning
Errors 30% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 92%
Best Practices Desktop Score 46%
SEO Desktop Score 89%
Progressive Web App Desktop Score 38%
Performance Mobile Score 75%
Best Practices Mobile Score 46%
SEO Mobile Score 86%
Progressive Web App Mobile Score 41%
Page Authority Authority 51%
Domain Authority Domain Authority 65%
Moz Rank 5.1/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 46 Characters
LIFE INSURANCE CORPORATION OF INDIA - होम
Meta Description 0 Characters
NO DATA
Effective URL 18 Characters
http://licindia.in
Excerpt Page content
Life Insurance Corporation of India - होम Javascript is not currently enabled in your browser. You must enable Javascript to run this web page correctly. ...
Keywords Cloud Density
प्लस18 बीमा12 जीवन10 योजनाएं9 करें9 पोर्टल6 जाने6 योजना6 प्रीमियम5 एजेंट5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
प्लस 18
बीमा 12
जीवन 10
योजनाएं 9
करें 9
पोर्टल 6
जाने 6
योजना 6
प्रीमियम 5
एजेंट 5
Google Preview Your look like this in google search result
LIFE INSURANCE CORPORATION OF INDIA - होम
http://licindia.in
Life Insurance Corporation of India - होम Javascript is not currently enabled in your browser. You must enable Javascript to run this web page correctly. ...
Robots.txt File Detected
http://licindia.in/robots.txt
Sitemap.xml File No Found
http://licindia.in/sitemap.xml
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2015-07-29 / 5 years
Create on: 2005-02-16 / 16 years
Expires on: 2025-02-16 / 49 months 10 days

Net4India ,IN
Registrar URL: http://www.net4.in

Nameservers
NS1.NET4INDIA.COM
NS2.NET4INDIA.COM
Page Size Code & Text Ratio
Document Size: ~59.79 KB
Code Size: ~43.8 KB
Text Size: ~15.99 KB Ratio: 26.75%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Does not use HTTPS 69 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Server response times are low (TTFB) Root document took 40 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 950 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 2,332 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 0 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 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
Properly size images Potential savings of 74 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoid enormous network payloads Total size was 3,255 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 19 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
Avoids an excessive DOM size 484 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 5 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 76 requests • 3,255 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 55 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 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
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Serve images in next-gen formats Potential savings of 2,550 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Mobile

Mobile Screenshot
First Contentful Paint (3G) 7626 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Tap targets are not sized appropriately 52% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 96.85% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Serve images in next-gen formats Potential savings of 2,550 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 69 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Server response times are low (TTFB) Root document took 40 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 2,332 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 40 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
Total Blocking Time 140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 16 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 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
Properly size images Potential savings of 49 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoid enormous network payloads Total size was 3,256 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.0 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 19 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
Avoids an excessive DOM size 484 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 5 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 4.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 76 requests • 3,256 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 55 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 4.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 200 OK
Date: Wed, 27 Nov 2019 21:14:26 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 22818
Cache-Control: private, no-store, must-revalidate
X-Frame-Options: SAMEORIGIN
Set-Cookie: ASP.NET_SessionId=3febgyzlipmlfcqm0st5mi0b; path=/; HttpOnly
X-UA-Compatible: IE=Edge
X-AspNet-Version: 4.0.30319
Vary: Accept-Encoding
Content-Encoding: gzip
Age: 27334
Server: v/52878/6.3.0/v6ord1-www
Accept-Ranges: bytes
X-Version: 4
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A licindia.in 64.185.181.238 IN 7147
NS licindia.in ns1.net4india.com IN 21599
NS licindia.in ns2.net4india.com IN 21599
MX licindia.in mail.net4india.com IN 21599
TXT licindia.in v=spf1 ip4:14.141.11.65 ip4:14.141.8.65 ip4:14.141.8.68 ip4:49.50.112.0/24 ip4:49.50.113.0/24 ip4:49.50.114.0/24 ip4:49.50.115.0/24 ip4:49.50.127.0/24 ip4:49.50.126.0/24 a mx -all IN 21599

Comments

Copyright © 2021 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome