Debate.com.mx - SEO Checker

Your Website Score is

Similar Ranking

NEW CARS, USED CARS, CAR DEALERS, PRICES & REVIEWS | CARS.COM

cars.com

DELFI ŽINIOS - PAGRINDINIS NAUJIENŲ PORTALAS LIETUVOJE

delfi.lt

NTTコミュニケーションズ　オフィシャルサイト

ntt.com

ギズモード・ジャパン | 日本最大級のガジェット＆テクノロジーサイト

gizmodo.jp

SCOOPWHOOP

scoopwhoop.com

BALENCIAGA OFFICIAL ONLINE BOUTIQUE

balenciaga.com

PRZYJAZNY DYSK INTERNETOWY - CHOMIKUJ.PL

chomikuj.pl

Latest Sites

LOSTCRYPTOESCROW | NO 1 ESCROW PLATFORM

lostcryptoescrow.com

BUY BEER, WINE, SPIRIT & GIFTS ONLINE - BOOZEBUD.COM

boozebud.com

CASINO REVIEWS AND GAME BONUSES - JENNYCASINO.COM

jennycasino.com

AMAZON.COM

amazon.com

powerofdream.co.id

BITMINEROPTIONS

bitmineroptions.com

欢迎访问本网站

gtr.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

70 debate.com.mx Last Updated: 1 year

Success 47% of passed verification steps

Warning 30% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 51%

Best Practices Desktop Score 69%

SEO Desktop Score 82%

Progressive Web App Desktop Score 46%

Performance Mobile Score 23%

Best Practices Mobile Score 77%

SEO Mobile Score 83%

Progressive Web App Mobile Score 44%

Page Authority Authority 48%

Domain Authority Domain Authority 81%

Moz Rank 4.8/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 65 Characters

DEBATE | LAS NOTICIAS DE MAYOR TRASCENDENCIA SOBRE ESTADOS UNIDOS

Meta Description 183 Characters

Entérate de las noticias más importantes de Arizona, California Florida, Nueva York y Texas. | Noticias de última hora, Primer Año de Gobiermo de AMLO, AMLO, Violencia contra la mujer

Effective URL 29 Characters

https://www.debate.com.mx/usa

Excerpt Page content

Debate | Las noticias de mayor trascendencia sobre Estados Unidos Estados Unidos Trump retira nominación para jefe del ICE Pedro Almodovar "Dolor y gloria", la película más ...

Keywords Cloud Density

hace44 minutos20 para14 debate13 hora13 miss11 horas9 universo8 noticias6 méxico6

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

Keyword	Freq	Title	Desc	Domain	H1	H2
hace	44
minutos	20
para	14
debate	13
hora	13
miss	11
horas	9
universo	8
noticias	6
méxico	6

Google Preview Your look like this in google search result

DEBATE | LAS NOTICIAS DE MAYOR TRASCENDENCIA SOBRE ESTADOS U

https://www.debate.com.mx/usa

Entérate de las noticias más importantes de Arizona, California Florida, Nueva York y Texas. | Noticias de última hora, Primer Año de Gobiermo de AMLO

Robots.txt File No Found

http://debate.com.mx/robots.txt

Sitemap.xml File No Found

http://debate.com.mx/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: 2017-06-16 / 4 years

Create on: 1995-03-31 / 26 years

Expires on: 2025-03-30 / 50 months 28 days

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

Empresas El Debate, S. A. de C. V. EMPRESAS EL DEBATE SA DE CV EMPRESAS EL DEBATE SA DE CV EMPRESAS EL DEBATE SA DE CV

Nameservers

david.ns.cloudflare.com

jessica.ns.cloudflare.com

Page Size Code & Text Ratio

Document Size: ~124.51 KB

Code Size: ~108.27 KB

Text Size: ~16.25 KB Ratio: 13.05%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

CloudFlare

CDN

comScore

Analytics

PWA - Manifest

EL DEBATE - USA Debate

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)

Param short_name

Debate

Param name

EL DEBATE - USA

Param background_color

#000e1c

Param orientation

portrait

Param theme_color

#000e1c

Param display

standalone

Param start_url

/?utm_source=web_app_manifest

Param gcm_sender_id

103953800507

Param gcm_user_visible_only

Desktop

First Meaningful Paint 0.9 s

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

Keep request counts low and transfer sizes small 250 requests • 4,662 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Use video formats for animated content Potential savings of 506 KB

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

Serve static assets with an efficient cache policy 38 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 80 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.9 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 29.1 s

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

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

Remove unused CSS Potential savings of 20 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

User Timing marks and measures 8 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

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

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

Eliminate render-blocking resources Potential savings of 20 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 126 KB

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

Minimize 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 120 ms

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

Reduce JavaScript execution time 2.0 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 1,391 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 154 KB

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

Speed Index 2.3 s

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

First CPU Idle 4.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).

Avoid enormous network payloads Total size was 4,662 KB

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

Minimize main-thread work 3.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 0.8 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 7 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

Avoid an excessive DOM size 1,485 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)

Mobile

Reduce JavaScript execution time 6.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 1,353 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 585 KB

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

Speed Index 9.9 s

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

First CPU Idle 13.3 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,586 KB

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

Minimize main-thread work 11.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 3.1 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 7 chains found

Avoid an excessive DOM size 1,482 elements

First Meaningful Paint 3.3 s

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

Keep request counts low and transfer sizes small 188 requests • 3,586 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 28 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 410 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 21.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 at 21.5 s

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

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

Tap targets are not sized appropriately 89% 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 99.98% 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 75 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

User Timing marks and measures 24 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

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

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

Eliminate render-blocking resources Potential savings of 210 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Reduce the impact of third-party code Third-party code blocked the main thread for 1,390 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 2,260 ms

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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

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: Sat, 07 Dec 2019 19:15:06 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=db84113bbbbd4683a3d0bf9bcc58f57411575746106; expires=Mon, 06-Jan-20 19:15:06 GMT; path=/; domain=.debate.com.mx; HttpOnly
Age: 0
cache-control: max-age=300, public, stale-while-revalidate=120, stale-if-error=84600
Last-Modified: Sat, 07 Dec 2019 19:14:19 GMT
Set-Cookie: JSESSIONID=08CCA0815F2CC90191D42D876285AFF3; Path=/; HttpOnly
Vary: Accept-Encoding
X-Cache: MISS
X-Cache-Hits: 0
X-Cacheable: YES
X-Cacheable-TTL: 300s
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Alt-Svc: h3-23=":443"; ma=86400
Server: cloudflare
CF-RAY: 5418d38ab96a9210-EWR
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	debate.com.mx	104.16.11.45	IN	226
A	debate.com.mx	104.16.10.45	IN	226
NS	debate.com.mx	david.ns.cloudflare.com	IN	69446
NS	debate.com.mx	jessica.ns.cloudflare.com	IN	69446
MX	debate.com.mx	alt1.aspmx.l.google.com	IN	120
MX	debate.com.mx	alt4.aspmx.l.google.com	IN	120
MX	debate.com.mx	aspmx.l.google.com	IN	120
MX	debate.com.mx	alt2.aspmx.l.google.com	IN	120
MX	debate.com.mx	alt3.aspmx.l.google.com	IN	120
TXT	debate.com.mx	google-site-verification=dB3DgS0tOGw-dwVuVxBOWlQPurPMYiHJZR3D7DFRNVU	IN	300
TXT	debate.com.mx	ca3-a6aca90372554ef2ab73006906c0bdb4	IN	300
TXT	debate.com.mx	debate.com.mx. IN TXT "v=spf1 mx a ip4:52.88.33.70/32 -all"	IN	300
TXT	debate.com.mx	v=spf1 a mx a:mgw.suantispam.com a:mx.suantispam.com a:kmxo.suantispam.com include:_pivote.suantispam.com include:_spf.google ~all	IN	300
AAAA	debate.com.mx	2606:4700::6810:b2d	IN	226
AAAA	debate.com.mx	2606:4700::6810:a2d	IN	226

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

70 debate.com.mx Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

CloudFlare

comScore

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments