Your Website Score is

Similar Ranking

85
GUCCI® US OFFICIAL SITE | REDEFINING MODERN LUXURY FASHION
gucci.com
85
THE STIR BY CAFEMOM
cafemom.com
85
THE EXPRESS TRIBUNE: ENGLISH NEWS & UPDATES WEBSITE IN PAKISTAN
tribune.com.pk
85
PLAYER FM - PODCAST SMARTER
player.fm
85
BEAUTY TIPS, CELEBRITY STYLE AND FASHION ADVICE FROM INSTYLE
instyle.com
85
HOME | THOMSON REUTERS
thomsonreuters.com
85
L'ÉQUIPE - L'ACTUALITÉ DU SPORT EN CONTINU.
lequipe.fr

Latest Sites

14
OSLOWAY | YOUR BEST LOCAL TOURS AND EXPERIENCES IN OSLO
osloway.no
22
JUST A MOMENT...
hourlyminer.com
33
ピアノ教室ネット|先生との出会いはここから。全国のピアノ教室から検索!
pnet.kawai.jp
19
ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|
adagiettopiano.com
33
ГЛАВНАЯ | UNIEX
uniex.biz
23
AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING
ahmadimado.net
19
DOGESILVA LIMITED - HOME
dogesilva.com

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

85 imss.gob.mx Last Updated: 8 months

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 98%
Best Practices Desktop Score 54%
SEO Desktop Score 100%
Progressive Web App Desktop Score 38%
Performance Mobile Score 69%
Best Practices Mobile Score 54%
SEO Mobile Score 96%
Progressive Web App Mobile Score 41%
Page Authority Authority 48%
Domain Authority Domain Authority 87%
Moz Rank 4.8/10
Bounce Rate Rate 0%
Title Tag 18 Characters
SITIO WEB DEL IMSS
Meta Description 117 Characters
El IMSS, es la institución con mayor presencia en la atención a la salud y en la protección social de los mexicanos.
Effective URL 18 Characters
http://imss.gob.mx
Excerpt Page content
Sitio Web del IMSS Header ...
Keywords Cloud Density
imss16 trámites8 sitio8 salud7 interés7 servicios7 para5 social4 transmisión4 inicio3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
imss 16
trámites 8
sitio 8
salud 7
interés 7
servicios 7
para 5
social 4
transmisión 4
inicio 3
Google Preview Your look like this in google search result
SITIO WEB DEL IMSS
http://imss.gob.mx
El IMSS, es la institución con mayor presencia en la atención a la salud y en la protección social de los mexicanos.
Robots.txt File Detected
Sitemap.xml File Detected
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: 2019-01-16 / 2 years
Create on: 1997-01-16 / 24 years
Expires on: 2020-01-15 / 7 months 0 days

Akky (Una division de NIC Mexico) ,Mexico Mexico Mexico Mexico

Instituto Mexicano del Seguro Social Instituto Mexicano del Seguro Social Instituto Mexicano del Seguro Social Instituto Mexicano del Seguro Social

Nameservers
imssns02.imss.gob.mx
201.144.5.43
imssns01.imss.gob.mx
201.144.5.42
imssdns01.imss.gob.mx
201.175.19.206
imssdns02.imss.gob.mx
201.175.19.207
Page Size Code & Text Ratio
Document Size: ~45.78 KB
Code Size: ~37.22 KB
Text Size: ~8.56 KB Ratio: 18.70%

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
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 328 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.8 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).
Avoids enormous network payloads Total size was 1,781 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.8 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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 20 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 610 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 22 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 74 requests • 1,781 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 58 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 0.8 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
Minify CSS Potential savings of 6 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 121 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 593 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 56 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 360 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 340 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 50 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 358 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 10 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

Mobile

Mobile Screenshot
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 30 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
First Contentful Paint (3G) 7890 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minify CSS Potential savings of 6 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 64% 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 100% 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
Remove unused CSS Potential savings of 90 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 593 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 56 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 140 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,530 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 358 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 50 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 310 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 210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.9 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 193 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 47 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.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).
Avoids enormous network payloads Total size was 1,581 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.7 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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 24 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 603 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 22 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 73 requests • 1,581 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 57 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive

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: Tue, 10 Dec 2019 00:18:28 GMT
Server: Apache/2.4.38 (Unix)
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
ETag: "b6cb-5994e6c5187fb"
Accept-Ranges: bytes
Content-Length: 46795
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Access-Control-Allow-Origin: *
Vary: Accept-Encoding
X-Cached-By: Boost
Content-Type: text/html; charset=utf-8
Set-Cookie: BIGipServerpool.app.portalweb.80=!d/pbzkFTv/+TvMBLEi2//faguU46sLh8T74W9q9BtilJv8K68FwZI7yh2b/XtvCubKoAKdqMzRX/gig=; path=/; Httponly
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome