todorelatos.com

todorelatos.com is SSL secured

Free website and domain report on todorelatos.com

Last Updated: 16th September, 2023 Update Now
Overview

Snoop Summary for todorelatos.com

This is a free and comprehensive report about todorelatos.com. The domain todorelatos.com is currently hosted on a server located in United States with the IP address 104.27.203.96, where USD is the local currency and the local language is English. Our records indicate that todorelatos.com is privately registered by Domains By Proxy, LLC. Todorelatos.com is expected to earn an estimated $308 USD per day from advertising revenue. The sale of todorelatos.com would possibly be worth $224,868 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Todorelatos.com receives an estimated 72,838 unique visitors every day - a massive amount of traffic! This report was last updated 16th September, 2023.

About todorelatos.com

Site Preview:
Title: Relatos Eroticos - TodoRelatos
Description: La mayor web de relatos eróticos en Castellano.
Keywords and Tags: adult content, popular, pornography
Related Terms: castellano, en castellano, produtos eroticos, quadrinhos eroticos, relatos, relatos de sexo, relatos eroticos, relatos sexuales, todopelishd castellano
Fav Icon:
Age: Over 22 years old
Domain Created: 7th June, 2001
Domain Updated: 23rd May, 2017
Domain Expires: 7th June, 2025
Review

Snoop Score

4/5 (Excellent!)

Valuation

$224,868 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 17,055
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 72,838
Monthly Visitors: 2,216,959
Yearly Visitors: 26,585,870
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $308 USD
Monthly Revenue: $9,375 USD
Yearly Revenue: $112,429 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: todorelatos.com 15
Domain Name: todorelatos 11
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.49 seconds
Load Time Comparison: Faster than 96% of sites

PageSpeed Insights

Avg. (All Categories) 64
Performance 100
Accessibility 39
Best Practices 73
SEO 82
Progressive Web App 27
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://todorelatos.com/
Updated: 9th April, 2021

1.27 seconds
First Contentful Paint (FCP)
67%
25%
8%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

100

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for todorelatos.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.6 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive todorelatos.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://todorelatos.com/
http/1.1
0
72.54299998749
673
0
301
https://todorelatos.com/
h2
73.17900005728
321.23000000138
9616
41418
200
text/html
Document
https://todorelatos.com/todorelatos20140224.css
h2
337.1970000444
396.53300005011
2865
22474
200
text/css
Stylesheet
https://todorelatos.com/js/add2home.css
h2
337.39899995271
380.82399999257
3566
6225
200
text/css
Stylesheet
https://todorelatos.com/js/add2home.js
h2
337.56200002972
427.14200005867
5909
14580
200
application/javascript
Script
https://todorelatos.com/info-icon.png
h2
397.98999996856
438.85000003502
1611
844
200
image/png
Image
https://todorelatos.com/images/logo1.gif
h2
428.44899999909
500.76700001955
10830
10061
200
image/gif
Image
https://todorelatos.com/images/clear.gif
h2
431.01699999534
457.24899997003
814
49
200
image/gif
Image
https://todorelatos.com/images/bullet_minisquare2.gif
h2
431.24700000044
460.28300002217
830
62
200
image/gif
Image
https://todorelatos.com/images/twitter-16.png
h2
431.3920000568
516.58599998336
1286
515
200
image/png
Image
https://todorelatos.com/images/bullet_minisquare_red.gif
h2
431.68999999762
474.34099996462
830
62
200
image/gif
Image
https://todorelatos.com/images/relatoshablados.png
h2
431.86899996363
463.45999999903
15675
14906
200
image/png
Image
https://todorelatos.com/images/amateur.png
h2
432.27500002831
462.64300006442
2802
2032
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-56P8SDH
h2
432.42800002918
444.65600000694
30492
77724
200
application/javascript
Script
https://ssl.google-analytics.com/ga.js
h2
432.66399996355
437.8110000398
17798
46274
200
text/javascript
Script
https://comunidad.todorelatos.com/promo/index/idPromo/4585
h2
444.01099998504
541.21399996802
10571
29256
200
text/html
Document
https://todorelatos.com/images/header-bg-ads.gif
h2
446.08999998309
499.56000002567
943
178
200
image/gif
Image
data
446.12400000915
446.18600001559
0
270
200
image/png
Image
https://todorelatos.com/images/header-bg-ads2.gif
h2
448.16499995068
476.05900000781
947
178
200
image/gif
Image
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1966430922&utmhn=todorelatos.com&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Relatos%20Er%C3%B3ticos%20-%20TodoRelatos&utmhid=102105764&utmr=-&utmp=%2F&utmht=1617936274094&utmac=UA-174762-3&utmcc=__utma%3D139792694.456675757.1617936274.1617936274.1617936274.1%3B%2B__utmz%3D139792694.1617936274.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=373841936&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
http/1.1
551.77699995693
572.81300006434
740
0
302
text/html
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-174762-3&cid=456675757.1617936274&jid=373841936&_v=5.7.2&z=1966430922
http/1.1
573.18299997132
583.74999999069
824
0
302
text/html
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-174762-3&cid=456675757.1617936274&jid=373841936&_v=5.7.2&z=1966430922
h2
584.03799997177
592.39000000525
678
42
200
image/gif
Image
https://comunidad.todorelatos.com/communities/c2KZzcu1xPaI1g3M0DuKjmKlzJkNIyzsScCIhljMBc//css/iframe_cams.css?v=202012011705
h2
585.22000000812
682.30700003915
30523
211454
200
text/css
Stylesheet
https://captures.vtsmedia.com/capture/2970227.1617936016.jpg?genre=C
h2
585.38800000679
668.02500002086
4696
4087
200
image/jpeg
Image
https://captures.vtsmedia.com/capture/2814546.1617936016.jpg?genre=W
h2
597.75700001046
680.00100005884
5052
4442
200
image/jpeg
Image
https://js-agent.newrelic.com/nr-1208.min.js
h2
709.66799999587
730.29199999291
12423
31332
200
application/javascript
Script
https://bam-cell.nr-data.net/1/192209e2f2?a=164572690&v=1208.49599aa&to=M1xXNkMCXBFRV0NdWQoWdhdCF10PH0RFW1sLFlwMVQZK&rst=298&ck=1&ref=https://comunidad.todorelatos.com/promo/index/idPromo/4585&ap=38&be=146&fe=267&dc=252&af=err,xhr,stn,ins&perf=%7B%22timing%22:%7B%22of%22:1617936273991,%22n%22:0,%22f%22:0,%22dn%22:0,%22dne%22:0,%22c%22:0,%22ce%22:0,%22rq%22:0,%22rp%22:99,%22rpe%22:99,%22dl%22:124,%22di%22:252,%22ds%22:252,%22de%22:252,%22dc%22:266,%22l%22:266,%22le%22:267%7D,%22navigation%22:%7B%7D%7D&fp=281&fcp=281&at=HxtUQAsYTx8%3D&jsonp=NREUM.setToken
http/1.1
742.16799996793
874.87099994905
646
57
200
text/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
353.174
8.31
365.491
5.456
457.575
16.518
474.107
47.138
530.971
11.846
546.81
33.776
583.895
9.462
594.028
7.53
602.42
5.593
613.525
11.908
712.639
10.184
722.86
6.079
728.95
8.283
762.395
8.792
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Todorelatos.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 13 KiB
Images can slow down the page's load time. Todorelatos.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://todorelatos.com/images/relatoshablados.png
14906
13564
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Todorelatos.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Todorelatos.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Todorelatos.com should consider minifying JS files.
Remove unused CSS — Potential savings of 29 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Todorelatos.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://comunidad.todorelatos.com/communities/c2KZzcu1xPaI1g3M0DuKjmKlzJkNIyzsScCIhljMBc//css/iframe_cams.css?v=202012011705
30523
29733
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 12 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://todorelatos.com/images/relatoshablados.png
14906
12182
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://todorelatos.com/
249.05
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Todorelatos.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://todorelatos.com/
190
https://todorelatos.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Todorelatos.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 170 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://comunidad.todorelatos.com/communities/c2KZzcu1xPaI1g3M0DuKjmKlzJkNIyzsScCIhljMBc//css/iframe_cams.css?v=202012011705
30523
https://www.googletagmanager.com/gtm.js?id=GTM-56P8SDH
30492
https://ssl.google-analytics.com/ga.js
17798
https://todorelatos.com/images/relatoshablados.png
15675
https://js-agent.newrelic.com/nr-1208.min.js
12423
https://todorelatos.com/images/logo1.gif
10830
https://comunidad.todorelatos.com/promo/index/idPromo/4585
10571
https://todorelatos.com/
9616
https://todorelatos.com/js/add2home.js
5909
https://captures.vtsmedia.com/capture/2814546.1617936016.jpg?genre=W
5052
Avoids an excessive DOM size — 659 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
659
Maximum DOM Depth
42
Maximum Child Elements
32
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Todorelatos.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://todorelatos.com/
95.315
3.412
2.229
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
70.963
Style & Layout
51.891
Other
48.587
Parse HTML & CSS
31.942
Rendering
21.951
Script Parsing & Compilation
11.593
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 26 requests • 170 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
26
173640
Script
5
67268
Image
13
46994
Stylesheet
3
36954
Document
2
20187
Other
3
2237
Media
0
0
Font
0
0
Third-party
9
73349
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
30492
0
18538
0
13069
0
824
0
678
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Todorelatos.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://ssl.google-analytics.com/ga.js
7200000
17798
https://js-agent.newrelic.com/nr-1208.min.js
7200000
12423
https://captures.vtsmedia.com/capture/2814546.1617936016.jpg?genre=W
86400000
5052
https://captures.vtsmedia.com/capture/2970227.1617936016.jpg?genre=C
86400000
4696
https://comunidad.todorelatos.com/communities/c2KZzcu1xPaI1g3M0DuKjmKlzJkNIyzsScCIhljMBc//css/iframe_cams.css?v=202012011705
691200000
30523
https://todorelatos.com/js/add2home.js
691200000
5909
https://todorelatos.com/js/add2home.css
691200000
3566
https://todorelatos.com/todorelatos20140224.css
691200000
2865
https://todorelatos.com/images/relatoshablados.png
7776000000
15675
https://todorelatos.com/images/logo1.gif
7776000000
10830
https://todorelatos.com/images/amateur.png
7776000000
2802
https://todorelatos.com/info-icon.png
7776000000
1611
https://todorelatos.com/images/twitter-16.png
7776000000
1286
https://todorelatos.com/images/header-bg-ads2.gif
7776000000
947
https://todorelatos.com/images/header-bg-ads.gif
7776000000
943
https://todorelatos.com/images/bullet_minisquare_red.gif
7776000000
830
https://todorelatos.com/images/bullet_minisquare2.gif
7776000000
830
https://todorelatos.com/images/clear.gif
7776000000
814
39

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of todorelatos.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Todorelatos.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
73

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that todorelatos.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://todorelatos.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://todorelatos.com/images/clear.gif
557 x 4
1 x 1
557 x 4

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for todorelatos.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of todorelatos.com on mobile screens.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
27

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of todorelatos.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of todorelatos.com on mobile screens.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 61
Performance 82
Accessibility 54
Best Practices 67
SEO 69
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://movil.todorelatos.com/index.php
Updated: 9th April, 2021

1.40 seconds
First Contentful Paint (FCP)
63%
31%
6%

0.01 seconds
First Input Delay (FID)
98%
2%
0%

82

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for todorelatos.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 3.4 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 70 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive todorelatos.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://todorelatos.com/
http/1.1
0
39.136000035796
677
0
301
https://todorelatos.com/
http/1.1
39.708000025712
255.44999999693
865
0
302
text/html
https://movil.todorelatos.com/index.php
h2
256.31300004898
560.49200001871
6452
35642
200
text/html
Document
https://movil.todorelatos.com/todorelatos20191124_movil.css?v=40
h2
581.16300002439
632.71000003442
3882
16047
200
text/css
Stylesheet
https://movil.todorelatos.com/js/add2home.css
h2
581.51500002714
668.72300003888
3578
6225
200
text/css
Stylesheet
https://movil.todorelatos.com/js/add2home.js
h2
581.72800001921
678.33500000415
5917
14580
200
application/javascript
Script
https://code.jquery.com/jquery-latest.js
h2
582.01400004327
605.62700004084
84321
282766
200
application/javascript
Script
https://movil.todorelatos.com/m/noticia.png
h2
670.22600001656
698.46600003075
3276
2495
200
image/png
Image
https://movil.todorelatos.com/m/link.png
h2
681.21300003259
757.95900000958
8857
8074
200
image/png
Image
https://movil.todorelatos.com/m/texto2.png
h2
684.60999999661
712.59700000519
2090
1302
200
image/png
Image
https://www.todorelatos.com/movil/foro.png
h2
684.83500002185
756.78799999878
2118
1339
200
image/png
Image
https://www.todorelatos.com/images/relatoshablados.png
h2
685.05200004438
763.54499999434
15686
14906
200
image/png
Image
https://www.todorelatos.com/images/amateur.png
h2
685.41500001447
764.47799999733
2807
2032
200
image/png
Image
https://movil.todorelatos.com/info-icon.png
h2
685.93200005125
789.41500000656
1619
844
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-56P8SDH
h2
686.23600003775
703.69900000514
30493
77724
200
application/javascript
Script
https://ssl.google-analytics.com/ga.js
h2
686.55400001444
690.82700001309
17798
46274
200
text/javascript
Script
https://www.todorelatos.com/images_movil/gradient_bg.gif
h2
722.63500001281
820.02899999497
5474
4700
200
image/gif
Image
https://www.todorelatos.com/images_movil/iPhoneToolbar.png
h2
722.96899999492
789.9220000254
1764
991
200
image/png
Image
https://www.todorelatos.com/images_movil/iPhoneButton.png
h2
723.5750000109
795.82400002982
2108
1338
200
image/png
Image
https://www.todorelatos.com/images_movil/iPhoneToolbar_footer2.png
h2
731.54400003841
865.61400000937
1781
1001
200
image/png
Image
data
731.60900000948
731.67900001863
0
270
200
image/png
Image
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=62082737&utmhn=movil.todorelatos.com&utmcs=windows-1252&utmsr=360x640&utmvp=360x640&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=TodoRelatos&utmhid=1909382808&utmr=-&utmp=%2Findex.php&utmht=1617936299207&utmac=UA-174762-3&utmcc=__utma%3D215767691.1920370479.1617936299.1617936299.1617936299.1%3B%2B__utmz%3D215767691.1617936299.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=706674251&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
http/1.1
816.36300001992
827.43600005051
739
0
302
text/html
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-174762-3&cid=1920370479.1617936299&jid=706674251&_v=5.7.2&z=62082737
http/1.1
827.75900000706
835.52700001746
823
0
302
text/html
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-174762-3&cid=1920370479.1617936299&jid=706674251&_v=5.7.2&z=62082737
h2
836.05000004172
842.50100003555
678
42
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
600.411
11.758
616.377
6.617
717.473
92.297
824.64
27.988
852.666
7.931
864.96
6.097
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 12 KiB
Images can slow down the page's load time. Todorelatos.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.todorelatos.com/images/relatoshablados.png
14906
12235
Defer offscreen images — Potential savings of 8 KiB
Time to Interactive can be slowed down by resources on the page. Todorelatos.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://movil.todorelatos.com/m/link.png
8074
8074
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Todorelatos.com should consider minifying CSS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Todorelatos.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 12 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.todorelatos.com/images/relatoshablados.png
14906
12182
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 310 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://movil.todorelatos.com/index.php
305.176
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Todorelatos.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 199 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://code.jquery.com/jquery-latest.js
84321
https://www.googletagmanager.com/gtm.js?id=GTM-56P8SDH
30493
https://ssl.google-analytics.com/ga.js
17798
https://www.todorelatos.com/images/relatoshablados.png
15686
https://movil.todorelatos.com/m/link.png
8857
https://movil.todorelatos.com/index.php
6452
https://movil.todorelatos.com/js/add2home.js
5917
https://www.todorelatos.com/images_movil/gradient_bg.gif
5474
https://movil.todorelatos.com/todorelatos20191124_movil.css?v=40
3882
https://movil.todorelatos.com/js/add2home.css
3578
Avoids an excessive DOM size — 687 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
687
Maximum DOM Depth
12
Maximum Child Elements
50
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Todorelatos.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://code.jquery.com/jquery-latest.js
295.98
101.956
24.788
https://movil.todorelatos.com/index.php
178.592
20.284
10.38
https://ssl.google-analytics.com/ga.js
113.24
104.084
6.252
Unattributable
101.108
7.168
1.216
https://www.googletagmanager.com/gtm.js?id=GTM-56P8SDH
68.356
50.912
9.34
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
288.004
Style & Layout
186.156
Other
154.828
Parse HTML & CSS
72.96
Script Parsing & Compilation
56.412
Rendering
20.216
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 23 requests • 199 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
23
203803
Script
4
138529
Image
12
48258
Stylesheet
2
7460
Document
1
6452
Other
4
3104
Media
0
0
Font
0
0
Third-party
6
134852
Minimize third-party usage — Third-party code blocked the main thread for 140 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
84321
86.356
18537
50.1
30493
0
823
0
678
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://movil.todorelatos.com/js/add2home.js
3943
185
https://ssl.google-analytics.com/ga.js
2970
112
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.6 s
The timing of the largest text or image that is painted.
Time to Interactive — 3.9 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 3.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 190 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.3 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 190 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Todorelatos.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://movil.todorelatos.com/js/add2home.js
5917
150
Minify JavaScript — Potential savings of 39 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Todorelatos.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://code.jquery.com/jquery-latest.js
84321
40175
Remove unused JavaScript — Potential savings of 52 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://code.jquery.com/jquery-latest.js
84321
53607

Diagnostics

Serve static assets with an efficient cache policy — 16 resources found
Todorelatos.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://ssl.google-analytics.com/ga.js
7200000
17798
https://code.jquery.com/jquery-latest.js
86400000
84321
https://movil.todorelatos.com/js/add2home.js
691200000
5917
https://movil.todorelatos.com/todorelatos20191124_movil.css?v=40
691200000
3882
https://movil.todorelatos.com/js/add2home.css
691200000
3578
https://www.todorelatos.com/images/relatoshablados.png
7776000000
15686
https://movil.todorelatos.com/m/link.png
7776000000
8857
https://www.todorelatos.com/images_movil/gradient_bg.gif
7776000000
5474
https://movil.todorelatos.com/m/noticia.png
7776000000
3276
https://www.todorelatos.com/images/amateur.png
7776000000
2807
https://www.todorelatos.com/movil/foro.png
7776000000
2118
https://www.todorelatos.com/images_movil/iPhoneButton.png
7776000000
2108
https://movil.todorelatos.com/m/texto2.png
7776000000
2090
https://www.todorelatos.com/images_movil/iPhoneToolbar_footer2.png
7776000000
1781
https://www.todorelatos.com/images_movil/iPhoneToolbar.png
7776000000
1764
https://movil.todorelatos.com/info-icon.png
7776000000
1619

Opportunities

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Todorelatos.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://todorelatos.com/
630
https://todorelatos.com/
480
https://movil.todorelatos.com/index.php
0

Other

First Contentful Paint (3G) — 6331 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
54

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of todorelatos.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Todorelatos.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
67

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that todorelatos.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://todorelatos.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://movil.todorelatos.com/m/noticia.png
32 x 26
32 x 26
64 x 52
https://movil.todorelatos.com/info-icon.png
16 x 16
16 x 16
32 x 32
https://www.todorelatos.com/images/amateur.png
16 x 16
20 x 20
32 x 32

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
69

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for todorelatos.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of todorelatos.com on mobile screens.
Document doesn't use legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
33

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of todorelatos.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of todorelatos.com on mobile screens.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.27.203.96
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Scottsdale
State: Arizona
Post Code: 85260
Email: TODORELATOS.COM@domainsbyproxy.com
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.0.20.224
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating: 3.9/5 (4 reviews)
WOT Trustworthiness: 78/100
WOT Child Safety: 15/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 6th August, 2020
Valid To: 6th August, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 5165989283594466982900891083407422727
Serial Number (Hex): 03E2EEEFB8CE0C3CA9C5F06D72A8F507
Valid From: 6th August, 2024
Valid To: 6th August, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Aug 6 06:41:37.227 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:60:C7:1B:B1:B3:C6:13:85:72:CA:E3:D6:
7E:FF:D0:59:98:34:2D:C1:C6:EC:58:41:B3:42:F3:E4:
72:33:1A:C4:02:20:7F:2D:B6:30:C8:C8:08:9A:CB:10:
DD:B1:64:A9:59:25:E5:D5:5D:34:DD:3C:77:4E:22:C1:
D9:95:BB:D7:B6:60
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Aug 6 06:41:37.181 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C1:4D:92:A0:66:F7:1A:E1:93:0D:CD:
9E:44:4C:03:2A:CA:2D:4B:54:E1:99:59:56:71:E0:6E:
C6:CD:48:A4:0F:02:21:00:85:1D:9C:CD:7F:47:16:B2:
00:9C:6A:7B:1A:35:9D:1B:C6:AB:AC:46:F5:9C:C7:6A:
4B:DE:92:B0:32:83:FF:D3
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:sni.cloudflaressl.com
DNS:todorelatos.com
DNS:*.todorelatos.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 9th April, 2021
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
CF-Cache-Status: DYNAMIC
cf-request-id: 09561d527c00003e21b3acc000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=wVKfj2ZUw%2BaHmLkv9DpJiVVjL3Xl%2FExsb8rq5MeIl1oMAYn1ttIY7rqWLLwO39%2Bb%2BL5gGVbZmuQlXzxaRWGN5LOtfym0lXTGikYLOturOgs%3D"}]}
NEL: {"report_to":"cf-nel","max_age":604800}
CF-RAY: 63d064ca59f53e21-EWR

Whois Lookup

Created: 7th June, 2001
Changed: 23rd May, 2017
Expires: 7th June, 2025
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: duke.ns.cloudflare.com
ruth.ns.cloudflare.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
14455 N. Hayden Road
Owner Post Code: 85260
Owner City: Scottsdale
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: TODORELATOS.COM@domainsbyproxy.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
14455 N. Hayden Road
Admin Post Code: 85260
Admin City: Scottsdale
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: TODORELATOS.COM@domainsbyproxy.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
14455 N. Hayden Road
Tech Post Code: 85260
Tech City: Scottsdale
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: TODORELATOS.COM@domainsbyproxy.com
Full Whois: Domain Name: TODORELATOS.COM
Registry Domain ID: 72104837_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2017-05-23T07:45:45Z
Creation Date: 2001-06-07T12:44:51Z
Registrar Registration Expiration Date: 2025-06-07T12:44:51Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 14455 N. Hayden Road
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: TODORELATOS.COM@domainsbyproxy.com
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 14455 N. Hayden Road
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: TODORELATOS.COM@domainsbyproxy.com
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 14455 N. Hayden Road
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: TODORELATOS.COM@domainsbyproxy.com
Name Server: DUKE.NS.CLOUDFLARE.COM
Name Server: RUTH.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-09T02:44:29Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
duke.ns.cloudflare.com 108.162.193.110
ruth.ns.cloudflare.com 108.162.192.143
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$10 USD 1/5
0/5
$1,173 USD 1/5
0/5
$6,660,599 USD 5/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address