Indat.mx - SEO Checker - Website Review

Your Website Score is

Similar Ranking

VIVILIA: REDACTOR FREELANCE - EMPLEO FREELANCE

vivilia.com

BLOG - INDAT

indat.mx

A LA CALLE – "VIAJAR TE DEJA SIN PALABRAS Y DESPUÉS TE CONVIERTE EN UN NARRADOR DE HISTORIAS" IBN BATTUTA

periodismoalacalle.wordpress.com

MARKETING ONLINE, CAMPAÑAS DE ADWORDS, DISEÑO Y MANTENIMIENTO WEB

virtualglobal.es

MAYÉUTIKA - HOME

mayeutika.biz

EVICERTIA - LOG ON

evicertia.com

IMNOVA.COM.AR

imnova.com.ar

Latest Sites

SCANDILAB | PICNICS & EVENTOS SOSTENIBLES EN MALLORCA

scandilab.com

HOME | SIMPLEXO TECHNOLOGIES

simplexo.tech

APPLE

apple.com

JUST A MOMENT...

nub8.net

CADENAS DE ORO | AURUS ORO LAMINADO 18K | CALI

aurus18k.com

DIGITAL PINEAPPLE - BLOG

blog.digital-pineapple.com.mx

VITAMINAS PROTEÍNAS NATURALES | NATURALPLUS - TIENDA ONLINE

naturalplus.beula.ec

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

81 indat.mx Last Updated: 2 years

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 59%

Best Practices Desktop Score 77%

SEO Desktop Score 90%

Progressive Web App Desktop Score 31%

Performance Mobile Score 6%

Best Practices Mobile Score 77%

SEO Mobile Score 91%

Progressive Web App Mobile Score 33%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 12 Characters

BLOG - INDAT

Meta Description 149 Characters

En Indat queremos potencializar la vida de las personas y organizaciones. ---izamos y desarrollamos estrategias de comunicación y marketing digital.

Effective URL 16 Characters

https://indat.mx

Excerpt Page content

Blog - Indat ...

Keywords Cloud Density

marketing18 tecnología14 análisis13 facebook13 read12 more12 indat11 noticias8 libra7 josé7

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
marketing	18
tecnología	14
análisis	13
facebook	13
read	12
more	12
indat	11
noticias	8
libra	7
josé	7

Google Preview Your look like this in google search result

BLOG - INDAT

https://indat.mx

En Indat queremos potencializar la vida de las personas y organizaciones. ---izamos y desarrollamos estrategias de comunicación y marketing digital.

Robots.txt File No Found

http://indat.mx/robots.txt

Sitemap.xml File No Found

http://indat.mx/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~87.48 KB

Code Size: ~71.84 KB

Text Size: ~15.65 KB Ratio: 17.88%

Social Data

Estimation Traffic and Earnings

Unique Visits

Daily

131

Pages Views

Daily

Income

Daily

1,988

Unique Visits

Monthly

3,734

Pages Views

Monthly

Income

Monthly

23,004

Unique Visits

Yearly

44,016

Pages Views

Yearly

Income

Yearly

Technologies

PWA - Manifest

Manifest is not valid

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

Desktop

First Meaningful Paint 2.5 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 68 requests • 2,274 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 22 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 2.5 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Links do not have descriptive text 1 link found

Descriptive link text helps search engines understand your content

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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.7 s

A fast page load over a cellular network ensures a good mobile user experience

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

Remove unused CSS Potential savings of 1,024 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

Server response times are low (TTFB) Root document took 270 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 1,260 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 1,114 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

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.2 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 16 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.5 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input

Avoids enormous network payloads Total size was 2,274 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 0.8 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

First Contentful Paint 2.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

Minimize Critical Requests Depth 29 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 442 elements

Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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)

Preload key requests Potential savings of 1,690 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

Minify JavaScript Potential savings of 7 KB

Minifying JavaScript files can reduce payload sizes and script parse time

Mobile

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 1,045 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

Server response times are low (TTFB) Root document took 90 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 7,470 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 1,114 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Third-Party Usage Third-party code blocked the main thread for 110 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 250 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 1.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

Defer offscreen images Potential savings of 55 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 10.2 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 14.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input

Avoids enormous network payloads Total size was 2,042 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 2.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 10.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

Minimize Critical Requests Depth 27 chains found

Avoids an excessive DOM size 442 elements

Preload key requests Potential savings of 6,990 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

Minify JavaScript Potential savings of 7 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 11.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 62 requests • 2,042 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 20 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 15.1 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Links do not have descriptive text 1 link found

Descriptive link text helps search engines understand your content

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

Page load is not fast enough on mobile networks Interactive at 15.1 s

A fast page load over a cellular network ensures a good mobile user experience

First Contentful Paint (3G) 22980 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 20 ms

Tap targets are not sized appropriately 97% 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

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

Congratulations! Your description is 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

Congratulations! Your site have Support to HTTPS

Headings

Congratulations! You are using your H1 and H2 tags in your site

Blacklist

Congratulations! Your site is not listed in a blacklist

W3C Validator

Congratulations! Your site not 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
https://indat.mx/blog/	Internal Link	200
INDAT	Internal Link	200
NOTICIAS	Internal Link	200
COLUMNAS Y ANÁLISIS	Internal Link	200
MARKETING Y TECNOLOGÍA	Internal Link	200
Análisis	Internal Link	200
El impacto de José José en Internet	Internal Link	200
Libra	Internal Link	200
Criptomoneda Libra podría retrasarse debido a presiones regulatorias	Internal Link	200
Instagram	Internal Link	200
Marketing	Internal Link	200
Nuevo: Anuncios de historias con botón a Messenger	Internal Link	200
Tecnología	Internal Link	200
Cómo crear un chatbot desde cero sin código	Internal Link	200
Facebook	Internal Link	200
Tecnología	Internal Link	200
¿Qué es Facebook Horizon? Conoce la nueva red social de realidad virtual	Internal Link	200
Análisis del público objetivo con herramientas online gratuitas	Internal Link	200
Indat	Internal Link	200
Page 2	Internal Link	200

Alexa Rank

0

Local Rank: / Users: / PageViews:

5,309,588

Global Rank

Domain Available

Domain (TDL) and Typo	Status
indat.co	Available Buy Now!
indat.us	Available Buy Now!
indat.com	Already Registered
indat.org	Already Registered
indat.net	Already Registered
idat.mx	Available Buy Now!
mndat.mx	Available Buy Now!
kndat.mx	Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/2 200 
server: nginx
date: Wed, 09 Oct 2019 15:09:31 GMT
content-type: text/html; charset=UTF-8
content-length: 13966
last-modified: Tue, 08 Oct 2019 19:11:33 GMT
accept-ranges: bytes
vary: Accept-Encoding
content-encoding: gzip
cache-control: max-age=0, no-cache, no-store, must-revalidate
pragma: no-cache
expires: Mon, 29 Oct 1923 20:30:00 GMT
x-powered-by: PleskLin

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	indat.mx	169.61.42.200	IN	285
NS	indat.mx	ns.indat.mx	IN	86400
MX	indat.mx	ALT2.ASPMX.L.GOOGLE.COM	IN	86400
MX	indat.mx	ASPMX2.GOOGLEMAIL.COM	IN	86400
MX	indat.mx	ASPMX3.GOOGLEMAIL.COM	IN	86400
MX	indat.mx	ASPMX.L.GOOGLE.COM	IN	86400
MX	indat.mx	ALT1.ASPMX.L.GOOGLE.COM	IN	86400
TXT	indat.mx	v=spf1 +a +mx -all	IN	86400

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

81 indat.mx Last Updated: 2 years

Desktop

Mobile

Social Data

Estimation Traffic and Earnings

Technologies

Font Awesome

Google Font API

Google Tag Manager

Ionicons

Nginx

PHP

Plesk

WordPress

Yoast SEO

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Alexa Rank

0

5,309,588

Domain Available

Information Server

About Us

Contact Info

Follow Us