Diagnóstico SEO

Your Website Score is

Similar Ranking

37
OCA | LAS BUENAS NOTICIAS LLEGAN
oca.com.ar
37
CIRUGÍA BARIÁTRICA DOMINICANA – MÁS DE 20 DE AÑOS DE EXCELENCIA DEDICADOS A TU SALUD
cirugiabariatricadominicana.com
37
PACADA | SOFOM,E.N.R.
pacada.com.mx
37
SINCRÓN DISEÑO ELECTRÓNICO
sincron.com.co
37
DIRECTORIO ASOCOPREN – PUBLICA, COMPRA Y VENDE
directorioasocopren.com
37
TBI ARCHITECTURE & ENGINEERING BARCELONA
teknobau.com
37
ACEX PERU/OUTSOURCING COMERCIO EXTERIOR/GESTION COMPRAS INTERNACIONALES/BENEFICIO EXONERACION PARA INSTITUCIONES INSTITUCIONES EDUCATIVAS/PROYECTOR CASIO LED/LASER/FLETE INTERNACIONAL/SEGURO TRANSPORT
acexperu.com

Latest Sites

99
FACEBOOK - LOG IN OR SIGN UP
facebook.com
44
-
pandorabox.chile
64
MERCADO LINEA – VENTA DE PRODUCTOS ONLINE
mercadolinea.cl
96
TIENDA YAMAHA
tienda-yamaha.com.co
69
PALLION
pallion.com.mx
69
FORMÉ - MEDICAL CENTER AND URGENT CARE
formemedicalcenter.com
76
MERCADONA
mercadona.com

Top Technologies

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

37 corporativodehospitales.com.mx Last Updated: 7 months

Success 31% of passed verification steps
Warning 23% of total warning
Errors 46% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 43%
Best Practices Desktop Score 79%
SEO Desktop Score 80%
Progressive Web App Desktop Score 11%
Performance Mobile Score 11%
Best Practices Mobile Score 71%
SEO Mobile Score 83%
Progressive Web App Mobile Score 14%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 38 Characters
HOSPITAL COVADONGA ::: BIENVENIDOS :::
Meta Description 0 Characters
NO DATA
Effective URL 37 Characters
http://corporativodehospitales.com.mx
Excerpt Page content
Hospital Covadonga ::: Bienvenidos ::: ...
Keywords Cloud Density
zoom8 para7 paquete6 checkup6 hospital6 clinica5 covadonga5 excelente5 años5 amable4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
zoom 8
para 7
paquete 6
checkup 6
hospital 6
clinica 5
covadonga 5
excelente 5
años 5
amable 4
Google Preview Your look like this in google search result
HOSPITAL COVADONGA ::: BIENVENIDOS :::
http://corporativodehospitales.com.mx
Hospital Covadonga ::: Bienvenidos ::: ...
Robots.txt File No Found
http://corporativodehospitales.com.mx/robots.txt
Sitemap.xml File No Found
http://corporativodehospitales.com.mx/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~31.99 KB
Code Size: ~21.12 KB
Text Size: ~10.87 KB Ratio: 33.98%

Social Data

Delicious Total: 0
Facebook Total: 58
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

96
Unique Visits
Daily
177
Pages Views
Daily
$0
Income
Daily
2,688
Unique Visits
Monthly
5,045
Pages Views
Monthly
$0
Income
Monthly
31,104
Unique Visits
Yearly
59,472
Pages Views
Yearly
$0
Income
Yearly

Technologies

Apache

Apache

Web Servers
Font Awesome

Font Awesome

Font Scripts
Google Font API

Google Font API

Font Scripts
jQuery

jQuery

JavaScript Frameworks
OWL Carousel

OWL Carousel

Widgets
Twitter Bootstrap

Twitter Bootstrap

Web Frameworks
YouTube

YouTube

Video Players

PWA - Manifest

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

Desktop

Desktop Screenshot
Avoid enormous network payloads Total size was 4,295 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
First Meaningful Paint 2.6 s
First Meaningful Paint measures when the primary content of a page is visible
Serve images in next-gen formats Potential savings of 1,008 KiB
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
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Estimated Input Latency 20 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 JavaScript Potential savings of 14 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Does not use HTTPS 53 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
Efficiently encode images Potential savings of 397 KiB
Optimized images load faster and consume less cellular data
Initial server response time was short Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Keep request counts low and transfer sizes small 81 requests • 4,295 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid chaining critical requests 31 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
Reduce the impact of third-party code Third-party code blocked the main thread for 340 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Enable text compression Potential savings of 1,228 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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
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
Serve static assets with an efficient cache policy 61 resources found
A long cache lifetime can speed up repeat visits to your page
Properly size images Potential savings of 541 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids an excessive DOM size 468 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)
First CPU Idle 3.5 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/).
Eliminate render-blocking resources Potential savings of 1,750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.017
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work 2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
JavaScript execution time 1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 4.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused CSS Potential savings of 1,011 KiB
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Largest Contentful Paint 5.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
User Timing marks and measures 5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Remove unused JavaScript Potential savings of 569 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 20.0 s
A fast page load over a cellular network ensures a good mobile user experience
Total Blocking Time 240 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify CSS Potential savings of 112 KiB
Minifying CSS files can reduce network payload sizes

Mobile

Mobile Screenshot
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time 940 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Contentful Paint 12.8 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused CSS Potential savings of 1,019 KiB
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
Minify CSS Potential savings of 112 KiB
Minifying CSS files can reduce network payload sizes
Document uses legible font sizes 99.62% 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
Avoids an excessive DOM size 455 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)
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
Serve static assets with an efficient cache policy 52 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
User Timing marks and measures 5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Time to Interactive 22.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 740 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce the impact of third-party code Third-party code blocked the main thread for 2,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
Serve images in next-gen formats Potential savings of 1,008 KiB
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
Avoid long main-thread tasks 15 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Remove unused JavaScript Potential savings of 589 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First CPU Idle 15.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/).
Estimated Input Latency 330 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
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Minify JavaScript Potential savings of 14 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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 Index 14.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 85 requests • 4,268 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Enable text compression Potential savings of 1,228 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce JavaScript execution time 4.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images Potential savings of 397 KiB
Optimized images load faster and consume less cellular data
Eliminate render-blocking resources Potential savings of 6,030 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize main-thread work 8.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Largest Contentful Paint 26.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Does not use HTTPS 53 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
Avoid enormous network payloads Total size was 4,268 KiB
Large network payloads cost users real money and are highly correlated with long load times
Tap targets are sized appropriately 100% 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
First Contentful Paint (3G) 27870 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Meaningful Paint 15.0 s
First Meaningful Paint measures when the primary content of a page is visible
Page load is not fast enough on mobile networks Interactive at 22.1 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid chaining critical requests 31 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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links
First 20 Links Relationship HTTP Status
http://corporativodehospitales.com.mx/index.html Internal Link 200
Quienes Somos Internal Link 200
Hospital Covadonga Cordoba Internal Link 200
Hospital Covadonga Orizaba Internal Link 200
Gabinete de Imagen Veracruz Internal Link 200
Historia Internal Link 200
Certificaciones y Galardones Internal Link 200
Especialidades Médicas Internal Link 200
Hospitalización Internal Link 200
Quirófanos Internal Link 200
Terapia Intensiva Internal Link 200
Terapia Intensiva Neonatal Internal Link 200
Unidad de Urgencias Internal Link 200
Sala de Inhaloterapia Internal Link 200
Gabinete Cardiológico Internal Link 200
Unidad de Hemodinamia Internal Link 200
Audiometría Internal Link 200
Laboratorio Análisis Clínicos Internal Link 200
Laboratorio de Análisis Patológicos Internal Link 200
Banco de Sangre Internal Link 200

Alexa Rank

0

Local Rank: / Users: / PageViews:

3,535,086

Global Rank

Domain Available

Domain (TDL) and Typo Status
corporativodehospitales.com.co Available Buy Now!
corporativodehospitales.com.us Available Buy Now!
corporativodehospitales.com.com Already Registered
corporativodehospitales.com.org Already Registered
corporativodehospitales.com.net Available Buy Now!
crporativodehospitales.com.mx Available Buy Now!
dorporativodehospitales.com.mx Available Buy Now!
rorporativodehospitales.com.mx Available Buy Now!

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, 13 Jan 2021 18:06:58 GMT
Server: Apache
Last-Modified: Mon, 09 Nov 2020 18:36:08 GMT
Accept-Ranges: bytes
Content-Length: 32672
Content-Type: text/html
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A corporativodehospitales.com.mx 67.217.34.44 IN 7108
NS corporativodehospitales.com.mx ns1-avatar.hosting-mexico.net IN 86400
NS corporativodehospitales.com.mx ns2-avatar.hosting-mexico.net IN 86400
MX corporativodehospitales.com.mx corporativodehospitales.com.mx IN 14400
TXT corporativodehospitales.com.mx v=spf1 ip4:67.217.34.44 ip4:216.245.221.162 +a +mx +ip4:216.245.221.163 +ip4:69.162.99.74 +include:4766.submission.antispamcloud.com +include:spf.antispamcloud.com ~all IN 14400

About Us

Somos una agencia de Marketing Digital especializada en Content Marketing e Inbound Marketing.

Contact Info

Genwords
Velez Sarsfield, 576 5000 Córdova
Argentina
CO +57 1 489 8266
MX +52 55 8526 5966
info@genwords.com

Follow Us

Twitter
Facebook
Linkedin
Instagram
© 2019 Genwords. Todos los derechos reservados.
Languages | English Español
  • Login/Register
  • Shortcuts Shortcut traffic Shortcut tips Shortcut alexa Shortcut server Shortcut meta Shortcut technologies Shortcut pagespeed Shortcut pagespeed_stats Shortcut social Shortcut domain_available
  • Languages English Español
...
Please wait
Starting process...