Diagnóstico SEO

Your Website Score is

Similar Ranking

71
angelsandrunes.com
71
sowiloservices.com
71
mlrecreacion.com
71
INSTAGRAM
instagram.com
71
INICIO
aburra.com
71
CERTUM SOLUTION GROUP SOLUCIONES DE NEGOCIOS BUSINESS COACHING
certum.com.mx
71
HOME
lonasrodriguez.com.mx

Latest Sites

76
AMERICANHYDROGENVZLA - INICIO
americanhydrogen.mozello.com
49
MUNDOTECNICO.INFO - FORO TÉCNICO REPARADOR - PÁGINA PRINCIPAL
mundotecnico.info
69
FACTURACIÓN DE EQUIPAJE A DOMICILIO - BOB
bob.io
86
STEBANSPORT.CO – TODAS LAS MARCAS EN UN SOLO LUGAR
stebansport.co
57
ILADIBA, EDUCACIÓN EN SALUD - ILADIBA
iladiba.com
57
SOLDADORAS INDUSTRIALES INFRA, S.A. DE C.V.
siisa-infra.com.mx
61
MAGIC CENTER - ELECTRODOMÉSTICOS Y MUEBLES PARA EL HOGAR
magiccenter.com.uy

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

71 robertdaniel.dev Last Updated: 5 days

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

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 87%
SEO Desktop Score 82%
Progressive Web App Desktop Score 36%
Performance Mobile Score 98%
Best Practices Mobile Score 80%
SEO Mobile Score 85%
Progressive Web App Mobile Score 42%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 24 Characters
https://robertdaniel.dev
Excerpt Page content
Coming SoonGet ready, something cool is coming!
Keywords Cloud Density
coming2 soon1 ready1 something1 cool1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
coming 2
soon 1
ready 1
something 1
cool 1
Google Preview Your look like this in google search result
robertdaniel.dev
https://robertdaniel.dev
Coming SoonGet ready, something cool is coming!
Robots.txt File Detected
http://robertdaniel.dev/robots.txt
Sitemap.xml File Detected
http://robertdaniel.dev/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~3.02 KB
Code Size: ~2.16 KB
Text Size: ~875 B Ratio: 28.33%

Social Data

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

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Technologies

CloudFlare

CloudFlare

CDN
PHP

PHP

Programming Languages
W3 Total Cache

W3 Total Cache

Cache Tools
WordPress

WordPress

CMS

PWA - Manifest

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

Desktop

Desktop Screenshot
Keep request counts low and transfer sizes small 6 requests • 104 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle 0.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/).
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoids enormous network payloads Total size was 104 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Eliminate render-blocking resources Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Does not use HTTPS 1 insecure request 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 served over 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
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
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
Initial server response time was short Root document took 220 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid chaining critical requests 3 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
Remove unused JavaScript Potential savings of 55 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Cumulative Layout Shift 0.021
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimizes main-thread work 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 13 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)
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Minify JavaScript Potential savings of 40 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint 0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused CSS Potential savings of 13 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

Mobile

Mobile Screenshot
Minimizes main-thread work 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 6 requests • 66 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
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 1.7 s
First Contentful Paint marks the time at which the first text or image is painted
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
Cumulative Layout Shift 0.159
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts 1 element found
These DOM elements contribute most to the CLS of the page.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
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
Avoids enormous network payloads Total size was 66 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 3 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
Eliminate render-blocking resources Potential savings of 770 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript Potential savings of 29 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
First Contentful Paint (3G) 3510 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 1.7 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Does not use HTTPS 1 insecure request 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 served over 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
Avoids an excessive DOM size 13 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 1.7 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/).
Initial server response time was short Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it
Remove unused CSS Potential savings of 13 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

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
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've 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
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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links
First 0 Links Relationship HTTP Status

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Domain Available

Domain (TDL) and Typo Status
robertdaniel.co Available Buy Now!
robertdaniel.us Already Registered
robertdaniel.com Already Registered
robertdaniel.org Available Buy Now!
robertdaniel.net Already Registered
rbertdaniel.dev Available Buy Now!
cobertdaniel.dev Available Buy Now!
fobertdaniel.dev 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: Sat, 20 Feb 2021 23:38:44 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=d9e75edf56a3035369f3540775ce154531613864324; expires=Mon, 22-Mar-21 23:38:44 GMT; path=/; domain=.robertdaniel.dev; HttpOnly; SameSite=Lax; Secure
X-Powered-By: W3 Total Cache/0.9.4.6.4
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Strict-Transport-Security: max-age=63072000; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-Turbo-Charged-By: LiteSpeed
CF-Cache-Status: DYNAMIC
cf-request-id: 08636865a0000029f7f7a61000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=6yrak3Amm%2Fg87J%2FLDuOLLYLr%2BRtL7656chlEMeOkmA9UeWpgQlC7qOpTIIxpHNYEmSonuGvM8TaTftmm3F%2Fqgm2f3iFnWD7t5HAXvZQr1d6H"}],"group":"cf-nel","max_age":604800}
NEL: {"max_age":604800,"report_to":"cf-nel"}
Server: cloudflare
CF-RAY: 624c101c3a3129f7-IAD
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A robertdaniel.dev 172.67.139.211 IN 241
A robertdaniel.dev 104.21.62.221 IN 241
NS robertdaniel.dev peter.ns.cloudflare.com IN 86400
NS robertdaniel.dev ali.ns.cloudflare.com IN 86400
MX robertdaniel.dev dc-210e07170214.robertdaniel.dev IN 300
TXT robertdaniel.dev v=spf1 +a +mx +ip4:70.32.23.73 ~all IN 300
AAAA robertdaniel.dev 2606:4700:3030::6815:3edd IN 241
AAAA robertdaniel.dev 2606:4700:3031::ac43:8bd3 IN 241

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