trendradars.com

trendradars.com is SSL secured

Free website and domain report on trendradars.com

Last Updated: 14th July, 2023 Update Now
Overview

Snoop Summary for trendradars.com

This is a free and comprehensive report about trendradars.com. Our records indicate that trendradars.com is owned/operated by Not available. Trendradars.com has the potential to be earning an estimated $9 USD per day from advertising revenue. If trendradars.com was to be sold it would possibly be worth $6,851 USD (based on the daily revenue potential of the website over a 24 month period). Trendradars.com receives an estimated 3,288 unique visitors every day - a large amount of traffic! This report was last updated 14th July, 2023.

About trendradars.com

Site Preview: trendradars.com trendradars.com
Title: TrendRadars - The Most Interesting Articles, Mysteries And Discoveries.
Description: TrendRadars discover Interesting Articles in science, space, technology, health, the environment, our culture and history.
Keywords and Tags: games
Related Terms: flickriver most interesting photos
Fav Icon:
Age: Over 3 years old
Domain Created: 25th February, 2021
Domain Updated: 10th February, 2023
Domain Expires: 25th February, 2024
Review

Snoop Score

2/5

Valuation

$6,851 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 184,959
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 28
Moz Page Authority: 43

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 3,288
Monthly Visitors: 100,076
Yearly Visitors: 1,200,120
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $9 USD
Monthly Revenue: $285 USD
Yearly Revenue: $3,420 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: trendradars.com 15
Domain Name: trendradars 11
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 79
Performance 92
Accessibility 96
Best Practices 92
SEO 82
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.trendradars.com
Updated: 29th August, 2022

2.17 seconds
First Contentful Paint (FCP)
68%
17%
15%

0.01 seconds
First Input Delay (FID)
94%
4%
2%

Simulate loading on desktop
92

Performance

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

Metrics

Time to Interactive — 1.7 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.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
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://trendradars.com/
http/1.1
0
69.253000008757
722
0
301
text/plain
https://trendradars.com/
http/1.1
69.690000003902
406.05600000708
841
0
301
text/html
https://www.trendradars.com/
http/1.1
406.48100001272
508.04400000197
1104
0
301
text/html
https://www.trendradars.com/channels/
h2
509.62300000538
596.64700001304
26561
207281
200
text/html
Document
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
h2
620.75900001219
689.2680000019
10356
29872
200
application/javascript
Script
https://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
h2
621.05700001121
728.14800000924
78669
529235
200
text/css
Stylesheet
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
h2
621.29300000379
642.41500000935
11325
88932
200
text/css
Stylesheet
https://c0.wp.com/c/6.0.1/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css
h2
621.50000000838
638.42200000363
2808
11256
200
text/css
Stylesheet
https://c0.wp.com/c/6.0.1/wp-includes/js/mediaelement/wp-mediaelement.min.css
h2
622.37300000561
638.87000000977
1396
4186
200
text/css
Stylesheet
https://c0.wp.com/p/jetpack/11.2/_inc/social-logos/social-logos.min.css
h2
623.04700000095
640.07700000366
8178
12106
200
text/css
Stylesheet
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
h2
623.24500000977
644.05700001225
15955
85690
200
text/css
Stylesheet
https://www.trendradars.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
h2
624.20100001327
696.09700000728
1472
1239
200
application/javascript
Script
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
717.35200000694
766.77300001029
4712
12332
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
717.52800000831
764.15800000541
5618
13970
200
text/javascript
Script
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
h2
717.74400000868
741.87800000072
28573
94160
200
text/javascript
Script
data
699.86600000993
700.15600000625
0
2914
200
text/css
Stylesheet
https://www.trendradars.com/cdn-cgi/apps/body/lsE3OJv2wob4-0W6GZUi-thC_Ps.js
h2
717.90200000396
776.23700001277
3177
6637
200
application/javascript
Script
data
788.57200000493
788.77199999988
0
1786
200
image/svg+xml
Image
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-brands-400.woff2
h2
838.31600000849
922.10100000375
77623
76764
200
font/woff2
Font
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-solid-900.woff2
h2
839.14999999979
931.38600001112
79059
78196
200
font/woff2
Font
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-regular-400.woff2
h2
840.48900000926
865.49100000411
14136
13276
200
font/woff2
Font
https://static.adsafeprotected.com/skeleton.js
h2
1114.6080000035
1133.2460000122
625
17
200
application/javascript
Script
https://stats.wp.com/e-202235.js
h2
1119.6470000141
1134.2460000014
3322
8970
200
application/javascript
Script
data
1173.2440000051
1173.4190000134
0
1117
200
text/css
Stylesheet
https://www.trendradars.com/channels/wp-content/plugins/litespeed-cache/guest.vary.php
h2
1184.3070000032
1800.7050000015
783
2
200
text/html
Fetch
https://www.trendradars.com/cdn-cgi/rum?
h2
1260.209
1295.5570000049
414
0
200
text/plain
XHR
https://colossalcoat.com/v2cdc9lMBaDg6eHseaDqBkuo8kIRx09mgBr5Iuo3HEUW0bGRdn0yURQXRkXyRX7focwuETjZg
h2
1354.4320000074
1396.7650000122
986
201
200
application/json
Fetch
https://colossalcoat.com/v2knr7q0JOst4638NpVb7o9XWSIS78f9hN5b__biSXRzjOqZdOueF8a13en4YaZB_z2dvDxqF
h2
1408.0840000097
1443.3750000026
689
3
200
application/json
Fetch
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)
610.965
21.157
694.434
7.831
703.234
16.674
722.484
9.947
732.444
28.181
761.524
241.093
1012.788
7.273
1020.074
8.193
1028.584
61.976
1091.45
19.155
1112.666
11.797
1124.487
48.784
1181.101
6.972
1189.902
54.085
1244.076
8.374
1320.744
27.899
1349.322
6.277
1399.744
9.556
1689.053
30.343
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Trendradars.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Trendradars.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Trendradars.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Trendradars.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 94 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Trendradars.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://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78669
69550
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
15955
15868
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
11325
11285
Reduce 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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 90 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://www.trendradars.com/channels/
88.015
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Trendradars.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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
92
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 370 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-solid-900.woff2
79059
https://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78669
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-brands-400.woff2
77623
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
28573
https://www.trendradars.com/channels/
26561
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
15955
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-regular-400.woff2
14136
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
11325
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
10356
https://c0.wp.com/p/jetpack/11.2/_inc/social-logos/social-logos.min.css
8178
Uses efficient cache policy on static assets — 3 resources found
Trendradars.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://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4712
https://www.trendradars.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1472
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Trendradars.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.1 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://www.trendradars.com/channels/
443.508
4.724
1.472
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
110.068
35.298
0.678
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
69.165
65.223
1.876
Unattributable
60.847
14.316
0.197
Minimizes main-thread work — 0.7 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)
Style & Layout
333.872
Script Evaluation
147.08
Other
143.426
Rendering
58.028
Parse HTML & CSS
55.028
Script Parsing & Compilation
6.862
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 — 25 requests • 370 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
25
379104
Font
3
170818
Stylesheet
6
118331
Script
8
57855
Document
1
26561
Other
7
5539
Image
0
0
Media
0
0
Third-party
11
79475
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)
39662
0
5618
0
3322
0
625
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00071531939281543
0.0002318324297197
0.0002318324297197
0.0002318324297197
0.00022069019132903
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://www.trendradars.com/channels/
701
121
https://stats.wp.com/e-202235.js
1889
54
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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of trendradars.com on mobile screens.
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.

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 — 1.3 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 560 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Trendradars.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://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78669
270
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
11325
230
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
10356
190
Avoid multiple page redirects — Potential savings of 570 ms
Redirects can cause additional delays before the page can begin loading. Trendradars.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://trendradars.com/
190
https://trendradars.com/
150
https://www.trendradars.com/
230
https://www.trendradars.com/channels/
0

Other

Avoid an excessive DOM size — 1,773 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
1773
Maximum DOM Depth
20
Maximum Child Elements
28
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of trendradars.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.
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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 alternate 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 `[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.
`<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"]`
Trendradars.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

Navigation

Heading elements are not 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.
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.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that trendradars.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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
WordPress
6.0.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://trendradars.com/
Allowed
82

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of trendradars.com on mobile screens.
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.

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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
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.

Content Best Practices

Links do not have descriptive text — 2 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.

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

PWA

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

PWA Optimized

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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of trendradars.com on 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
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) 73
Performance 56
Accessibility 96
Best Practices 92
SEO 83
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.trendradars.com
Updated: 29th August, 2022

2.41 seconds
First Contentful Paint (FCP)
66%
16%
18%

0.05 seconds
First Input Delay (FID)
86%
10%
4%

Simulate loading on mobile
56

Performance

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

Metrics

Cumulative Layout Shift — 0.066
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Trendradars.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Trendradars.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Trendradars.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Trendradars.com should consider minifying JS files.
Reduce 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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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 80 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://www.trendradars.com/channels/
81.799
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Trendradars.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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
92
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 370 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-solid-900.woff2
79061
https://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78669
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-brands-400.woff2
77623
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
28569
https://www.trendradars.com/channels/
26607
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
15955
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-regular-400.woff2
14132
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
11325
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
10364
https://c0.wp.com/p/jetpack/11.2/_inc/social-logos/social-logos.min.css
8178
Uses efficient cache policy on static assets — 3 resources found
Trendradars.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://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
86400000
5618
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
172800000
4704
https://www.trendradars.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1472
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Trendradars.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.7 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://www.trendradars.com/channels/
1588.14
14.54
4.712
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
431.532
125.072
2.556
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
315.684
204.424
6.82
Unattributable
244.796
54.224
0.736
https://www.trendradars.com/cdn-cgi/apps/body/lsE3OJv2wob4-0W6GZUi-thC_Ps.js
190.66
185.82
0.788
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
85.62
74.444
7.62
https://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78.436
0
0
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 — 25 requests • 370 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
25
379128
Font
3
170816
Stylesheet
6
118331
Script
8
57863
Document
1
26607
Other
7
5511
Image
0
0
Media
0
0
Third-party
11
79466
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)
39662
0
5618
0
3322
0
625
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.015449125301358
0.013655730336305
0.013396444317261
0.012424121745847
0.011115344697341
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 — 11 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://www.trendradars.com/channels/
2287
385
https://stats.wp.com/e-202235.js
6969
259
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
5957
232
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
5280
135
https://www.trendradars.com/channels/
2672
127
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
4946
98
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
5876
81
https://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
3501
78
https://www.trendradars.com/channels/
2220
67
https://www.trendradars.com/channels/
3450
51
https://www.trendradars.com/channels/
2799
50
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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of trendradars.com on mobile screens.
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.

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.

Audits

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://trendradars.com/
http/1.1
0
102.24299971014
728
0
301
text/plain
https://trendradars.com/
http/1.1
102.71900007501
401.42299979925
833
0
301
text/html
https://www.trendradars.com/
http/1.1
401.89399989322
529.63300002739
1075
0
301
text/html
https://www.trendradars.com/channels/
h2
530.10799968615
610.91500008479
26607
207280
200
text/html
Document
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
h2
625.78699970618
664.71799975261
10364
29872
200
application/javascript
Script
https://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
h2
626.05299986899
702.39199977368
78669
529235
200
text/css
Stylesheet
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
h2
626.34699977934
646.28499979153
11325
88932
200
text/css
Stylesheet
https://c0.wp.com/c/6.0.1/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css
h2
626.61099992692
643.49999977276
2808
11256
200
text/css
Stylesheet
https://c0.wp.com/c/6.0.1/wp-includes/js/mediaelement/wp-mediaelement.min.css
h2
626.92599976435
642.30499975383
1396
4186
200
text/css
Stylesheet
https://c0.wp.com/p/jetpack/11.2/_inc/social-logos/social-logos.min.css
h2
627.23500002176
643.99999985471
8178
12106
200
text/css
Stylesheet
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
h2
627.41199973971
648.38199969381
15955
85690
200
text/css
Stylesheet
https://www.trendradars.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
h2
627.77199968696
645.40700009093
1472
1239
200
application/javascript
Script
https://www.trendradars.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js
h2
668.40100008994
692.44299968705
4704
12332
200
application/javascript
Script
https://static.cloudflareinsights.com/beacon.min.js/v652eace1692a40cfa3763df669d7439c1639079717194
h2
686.71899987385
730.59300007299
5618
13970
200
text/javascript
Script
https://colossalcoat.com/v2ltjLiLQkqw3Kstwab60-iJlNz26rLggHdZxsv5iLlMEdHI_buA03B8
h2
686.90899992362
708.69999984279
28569
94160
200
text/javascript
Script
data
673.64999977872
673.90900012106
0
2914
200
text/css
Stylesheet
https://www.trendradars.com/cdn-cgi/apps/body/lsE3OJv2wob4-0W6GZUi-thC_Ps.js
h2
687.03999975696
719.42699979991
3189
6637
200
application/javascript
Script
data
744.15999976918
744.34599978849
0
1786
200
image/svg+xml
Image
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-brands-400.woff2
h2
788.94399991259
817.68899969757
77623
76764
200
font/woff2
Font
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-solid-900.woff2
h2
789.7520000115
823.64999968559
79061
78196
200
font/woff2
Font
https://www.trendradars.com/channels/wp-content/themes/chromenews/assets/font-awesome/webfonts/fa-regular-400.woff2
h2
790.46799987555
837.51899981871
14132
13276
200
font/woff2
Font
data
1028.1289997511
1028.3069997095
0
1117
200
text/css
Stylesheet
https://static.adsafeprotected.com/skeleton.js
h2
1081.0340000317
1096.0240000859
625
17
200
application/javascript
Script
https://stats.wp.com/e-202235.js
h2
1084.6289996989
1099.026999902
3322
8970
200
application/javascript
Script
https://www.trendradars.com/channels/wp-content/plugins/litespeed-cache/guest.vary.php
h2
1154.9859996885
1264.1859999858
791
2
200
text/html
Fetch
https://www.trendradars.com/cdn-cgi/rum?
h2
1263.2639999501
1283.2439998165
414
0
200
text/plain
XHR
https://colossalcoat.com/v2qpkfLWzAGgxFRKMyowMK1Rayvq15WzdpmV3anmxf5T8SSYx6SnWkGfdEy9TWITepKEVKX7X
h2
1313.631999772
1331.851999741
981
201
200
application/json
Fetch
https://colossalcoat.com/v2pvwuP4PqCbEbc-0PSYhAUlOve5b5D89RCdtWSO9EsVdjWUsYQHT_Sa2mhcZoFCvJKcDY2VO
h2
1341.7969997972
1355.3299997002
689
3
200
application/json
Fetch
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)
616.244
16.794
669.733
6.532
676.359
12.71
690.985
6.55
705.105
19.609
725.369
192.412
924.459
6.478
930.95
8.153
941.84
63.551
1006.937
20.224
1030.238
49
1079.249
57.93
1137.671
8.202
1152.403
33.746
1187.316
64.676
1283.868
23.718
1334.886
8.404
1683.869
24.819
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 6.5 s
The time taken for the page to become fully interactive.
Speed Index — 4.9 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 380 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).

Other

Reduce unused CSS — Potential savings of 93 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Trendradars.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://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78669
68308
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
15955
15868
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
11325
11285
Minimize main-thread work — 3.0 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)
Style & Layout
1327.768
Script Evaluation
686.096
Other
562.104
Rendering
213.14
Parse HTML & CSS
157.652
Script Parsing & Compilation
26.008

Metrics

First Contentful Paint — 4.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 5.1 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 260 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.9 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 2,280 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Trendradars.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://www.trendradars.com/channels/wp-content/litespeed/css/fbaa7b7fba4de436a7f677c5c76345ff.css?ver=a46a3
78669
1230
https://c0.wp.com/c/6.0.1/wp-includes/css/dist/block-library/style.min.css
11325
930
https://c0.wp.com/p/jetpack/11.2/_inc/social-logos/social-logos.min.css
8178
150
https://c0.wp.com/p/jetpack/11.2/css/jetpack.css
15955
150
https://www.trendradars.com/cdn-cgi/apps/head/sVccIBjuF-ZD9O9cYascrzpkmEI.js
10364
630
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Trendradars.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://trendradars.com/
630
https://trendradars.com/
480
https://www.trendradars.com/
780
https://www.trendradars.com/channels/
0
Avoid an excessive DOM size — 1,773 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
1773
Maximum DOM Depth
20
Maximum Child Elements
28
First Contentful Paint (3G) — 9900 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
96

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of trendradars.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.
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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 alternate 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 `[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.
`<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"]`
Trendradars.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

Navigation

Heading elements are not 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.
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.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that trendradars.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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
WordPress
6.0.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://trendradars.com/
Allowed
83

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of trendradars.com on mobile screens.
Document uses legible font sizes — 84.57% legible text
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.
Source Selector % of Page Text Font Size
.read-img a.aft-post-image-link
13.87%
0px
1.56%
< 12px
84.57%
≥ 12px

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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
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

Tap targets are not sized appropriately — 89% appropriately sized tap targets
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.
Tap Target Size Overlapping Target
UK
14x30
14x30
14x30
14x30
14x30
14x30
14x30
14x30
14x30
67x16
67x16
63x16
82x16
151x16
136x16
100x16
95x16
87x16
63x16
79x16
UK
28x30
US
UK
28x30

Content Best Practices

Links do not have descriptive text — 2 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.

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

PWA

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

PWA Optimized

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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of trendradars.com on 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
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.21.85.205
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Not available
Country: CN
City:
State: ShangHai
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
22net, Inc. 43.240.73.100
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.trendradars.com
Issued By: GTS CA 1P5
Valid From: 19th March, 2023
Valid To: 17th June, 2023
Subject: CN = *.trendradars.com
Hash: 6ef89283
Issuer: CN = GTS CA 1P5
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 113972164871641439316404851332208039
Serial Number (Hex): 15F342F66084DF0E376B6812F9D5A7
Valid From: 19th March, 2024
Valid To: 17th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:D5:FC:9E:0D:DF:1E:CA:DD:08:97:97:6E:2B:C5:5F:C5:2B:F5:EC:B8
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1p5/Hy6Rl693DM4.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/s/gts1p5/0C_ovNzblsU
CA Issuers - URI:http://pki.goog/repo/certs/gts1p5.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Mar 19 17:19:34.009 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D2:06:3D:50:AC:0F:5D:31:1D:CA:3C:
FA:82:73:CE:85:26:61:8E:67:90:10:E0:42:A1:B0:6F:
42:7D:63:7A:7C:02:20:15:E4:8F:10:62:59:3D:03:0A:
2A:B2:F2:24:C2:B6:BB:01:D3:F2:BD:AB:D4:B9:5A:3B:
65:B0:A0:9C:75:E9:0F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Mar 19 17:19:34.017 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:41:9D:04:F4:F8:37:58:0A:52:D1:AB:79:
53:A6:93:F9:03:26:8D:FC:7A:CD:8E:12:BD:7C:B7:24:
91:E8:A4:17:02:20:48:03:5B:C7:45:B1:57:A3:0D:10:
9C:2E:AF:99:6E:C5:AE:7D:16:FE:83:5E:33:31:AD:A2:
31:31:09:29:18:6C
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:trendradars.com
DNS:*.trendradars.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
Date: 1st May, 2023
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
location: http://www.trendradars.com/
strict-transport-security: max-age=31536000
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=eegFQJ61YT8unBC2jxAUogb6kRZDrdkOiy7tygMwAr3jihZwwgUeeWC4QVU3DkZ%2Bm3i1ruN22bt7HA57GJWC5l2uXYkvqXaCYABfBxvPJ0y5GdJp4OckMtQVe8UnLBAda8I%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7c07bd966df232fa-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 25th February, 2021
Changed: 10th February, 2023
Expires: 25th February, 2024
Registrar: 22net, Inc.
Status: ok
Nameservers: guy.ns.cloudflare.com
rihana.ns.cloudflare.com
Full Whois: Domain Name: TRENDRADARS.COM
Registry Domain ID: 2593852051_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.22.cn
Registrar URL: http://www.22.cn
Updated Date: 2023-02-10T03:01:02Z
Creation Date: 2021-02-25T03:04:23Z
Registry Expiry Date: 2024-02-25T03:04:23Z
Registrar: 22net, Inc.
Registrar IANA ID: 1555
Registrar Abuse Contact Email: abuse@22.cn
Registrar Abuse Contact Phone: +86.571.88276020
Domain Status: ok https://icann.org/epp#ok
Name Server: GUY.NS.CLOUDFLARE.COM
Name Server: RIHANA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2023-05-01T11:38:45Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
guy.ns.cloudflare.com 108.162.193.173
rihana.ns.cloudflare.com 108.162.192.244
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address