ytmp3.rocks

ytmp3.rocks is SSL secured

Free website and domain report on ytmp3.rocks

Last Updated: 4th August, 2021 Update Now
Overview

Snoop Summary for ytmp3.rocks

This is a free and comprehensive report about ytmp3.rocks. The domain ytmp3.rocks is currently hosted on a server located in United States with the IP address 104.21.4.132, where the local currency is USD and English is the local language. If ytmp3.rocks was to be sold it would possibly be worth $405 USD (based on the daily revenue potential of the website over a 24 month period). Ytmp3.rocks is somewhat popular with an estimated 190 daily unique visitors. This report was last updated 4th August, 2021.

About ytmp3.rocks

Site Preview: ytmp3.rocks ytmp3.rocks
Title: Ytmp3 - Youtube to Mp3 Converter Online tool for Free
Description: ytmp3 is a free youtube to mp3 downloader which helps you to convert youtube mp3. Also Download yt to mp3, youtube downloader, youtube to mp3
Keywords and Tags:
Related Terms: how to repeat youtube videos, listen on repeat youtube, play youtube on repeat, tool youtube, uniccshop youtube, youtube analytics tool, youtube facebook share, youtube mp3 y mp4 online converter, youtube seo tool, youtube to mo3
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$405 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,607,638
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: 190
Monthly Visitors: 5,783
Yearly Visitors: 69,350
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $16 USD
Yearly Revenue: $198 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: ytmp3.rocks 11
Domain Name: ytmp3 5
Extension (TLD): rocks 5

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 75
Performance 100
Accessibility 85
Best Practices 73
SEO 83
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://ytmp3.rocks/
Updated: 4th August, 2021

2.10 seconds
First Contentful Paint (FCP)
69%
22%
9%

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

Simulate loading on desktop
100

Performance

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

Metrics

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

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
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://ytmp3.rocks/
http/1.1
0
67.459000041708
768
0
301
https://ytmp3.rocks/
h2
68.239000043832
618.36900003254
3845
9543
200
text/html
Document
https://ytmp3.rocks/template/sober/css/app.css
h2
638.12800007872
776.97900007479
53958
315615
200
text/css
Stylesheet
https://ytmp3.rocks/template/sober/css/font-awesome.css
h2
638.43599997927
757.99900002312
13660
58881
200
text/css
Stylesheet
https://ytmp4.top/template/sober/img/download.jpg
h2
640.91600000393
743.04299999494
19232
18309
200
image/jpeg
Image
https://www.googletagmanager.com/gtag/js?id=UA-203090593-1
h2
641.35000004899
660.32200003974
41434
102579
200
application/javascript
Script
https://ytmp3.rocks/sw.js
h2
639.90199996624
779.65899999253
61267
138522
200
application/javascript
Script
https://ytmp3.rocks/template/sober/js/compressed.js
h2
640.36700001452
723.08500006329
61229
189911
200
application/javascript
Script
https://ytmp3.rocks/template/sober/js/app.js
h2
640.58200002182
702.36700004898
3707
15886
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
855.8830000693
861.43300007097
20324
49389
200
text/javascript
Script
https://ouwithh.club/aFhWaDATeiUfbx0qOkoKSjAiHEAbYnlHSRw1JlseGjc1A0NHKyFGWht6ekpDBT50UgFEeiUFRkpidFseX3p6SkQJPwkBVEpidFEAUW1nURJEeiUdUjcxMloSUnoyXgRYYGRQCUVtMFhURWxlWAZFOWFbCUVtYVBSCTtvXglfYWZKTQ
h2
875.55500003509
1012.5160000753
21825
57189
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j92&a=99459296&t=pageview&_s=1&dl=https%3A%2F%2Fytmp3.rocks%2F&ul=en-us&de=UTF-8&dt=Ytmp3%20-%20Youtube%20to%20Mp3%20Converter%20Online%20tool%20for%20Free&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=1430685547&gjid=1806244725&cid=414918220.1628100230&tid=UA-203090593-1&_gid=1834460765.1628100230&_r=1&gtm=2ou820&z=524042272
h2
951.55800005887
956.79800002836
636
1
200
text/plain
XHR
https://ellenince.biz/utx?tid=909519&top=ytmp3.rocks&cb=hfSmSbFLoNGZ
h2
1040.542999981
1135.5530000292
1138
0
204
text/plain
XHR
https://ewledgeand.top/
h2
1051.0899999645
1108.3130000625
65
0
200
text/plain
XHR
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)
630.813
8.875
680.713
10.195
787.366
17.434
805.737
46.532
852.321
12.3
864.816
48.926
915.773
10.939
928.475
32.22
1028.482
21.419
1871.641
8.962
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.

Opportunities

Eliminate render-blocking resources — Potential savings of 50 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ytmp3.rocks 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://ytmp3.rocks/template/sober/css/app.css
53958
80
Properly size images
Images can slow down the page's load time. Ytmp3.rocks should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ytmp3.rocks should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ytmp3.rocks should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ytmp3.rocks should consider minifying JS files.
Reduce unused CSS — Potential savings of 65 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ytmp3.rocks 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://ytmp3.rocks/template/sober/css/app.css
53958
52735
https://ytmp3.rocks/template/sober/css/font-awesome.css
13660
13660
Reduce unused JavaScript — Potential savings of 103 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://ytmp3.rocks/template/sober/js/compressed.js
61229
42388
https://ytmp3.rocks/sw.js
61267
41222
https://www.googletagmanager.com/gtag/js?id=UA-203090593-1
41434
22027
Efficiently encode images — Potential savings of 5 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://ytmp4.top/template/sober/img/download.jpg
18309
4877
Serve images in next-gen formats — Potential savings of 11 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://ytmp4.top/template/sober/img/download.jpg
18309
11193
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 550 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://ytmp3.rocks/
551.127
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Ytmp3.rocks should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ytmp3.rocks/
190
https://ytmp3.rocks/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ytmp3.rocks 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://ytmp3.rocks/template/sober/js/compressed.js
54
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 296 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://ytmp3.rocks/sw.js
61267
https://ytmp3.rocks/template/sober/js/compressed.js
61229
https://ytmp3.rocks/template/sober/css/app.css
53958
https://www.googletagmanager.com/gtag/js?id=UA-203090593-1
41434
https://ouwithh.club/aFhWaDATeiUfbx0qOkoKSjAiHEAbYnlHSRw1JlseGjc1A0NHKyFGWht6ekpDBT50UgFEeiUFRkpidFseX3p6SkQJPwkBVEpidFEAUW1nURJEeiUdUjcxMloSUnoyXgRYYGRQCUVtMFhURWxlWAZFOWFbCUVtYVBSCTtvXglfYWZKTQ
21825
https://www.google-analytics.com/analytics.js
20324
https://ytmp4.top/template/sober/img/download.jpg
19232
https://ytmp3.rocks/template/sober/css/font-awesome.css
13660
https://ytmp3.rocks/
3845
https://ytmp3.rocks/template/sober/js/app.js
3707
Avoids an excessive DOM size — 95 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
95
Maximum DOM Depth
9
Maximum Child Elements
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ytmp3.rocks 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://ytmp3.rocks/
78.284
14.841
1.644
Minimizes main-thread work — 0.3 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
139.767
Style & Layout
44.851
Other
34.206
Parse HTML & CSS
27.022
Script Parsing & Compilation
15.896
Rendering
3.34
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 — 14 requests • 296 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
14
303088
Script
6
209786
Stylesheet
2
67618
Image
1
19232
Document
1
3845
Other
4
2607
Media
0
0
Font
0
0
Third-party
7
104654
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)
41434
0
20960
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.

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 — 8 resources found
Ytmp3.rocks 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://ouwithh.club/aFhWaDATeiUfbx0qOkoKSjAiHEAbYnlHSRw1JlseGjc1A0NHKyFGWht6ekpDBT50UgFEeiUFRkpidFseX3p6SkQJPwkBVEpidFEAUW1nURJEeiUdUjcxMloSUnoyXgRYYGRQCUVtMFhURWxlWAZFOWFbCUVtYVBSCTtvXglfYWZKTQ
0
21825
https://www.google-analytics.com/analytics.js
7200000
20324
https://ytmp3.rocks/sw.js
604800000
61267
https://ytmp3.rocks/template/sober/js/compressed.js
604800000
61229
https://ytmp3.rocks/template/sober/css/app.css
604800000
53958
https://ytmp4.top/template/sober/img/download.jpg
604800000
19232
https://ytmp3.rocks/template/sober/css/font-awesome.css
604800000
13660
https://ytmp3.rocks/template/sober/js/app.js
604800000
3707

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://ytmp4.top/template/sober/img/download.jpg
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ytmp3.rocks. 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.
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 `[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 `[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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ytmp3.rocks 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

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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 ytmp3.rocks 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 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

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
Bootstrap
4.3.1
jQuery
3.5.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://ytmp3.rocks/template/sober/js/compressed.js
https://ytmp3.rocks/template/sober/js/_site_kit_free/assets/js/kit-free.js.map
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://ytmp3.rocks/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Requests 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.
Source

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
ReferenceError: flatpickr is not defined at HTMLDocument.<anonymous> (https://ytmp3.rocks/template/sober/js/compressed.js:22:3233) at e (https://ytmp3.rocks/template/sober/js/compressed.js:2:30005) at t (https://ytmp3.rocks/template/sober/js/compressed.js:2:30307)
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ytmp3.rocks. 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 ytmp3.rocks 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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the 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.

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.
robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
2
Sitemap: /sitemap.xml
Invalid sitemap URL

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

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 ytmp3.rocks. 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.
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 ytmp3.rocks on mobile screens.

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 provide 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.
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 86
Accessibility 89
Best Practices 73
SEO 86
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://ytmp3.rocks/
Updated: 4th August, 2021

2.55 seconds
First Contentful Paint (FCP)
45%
38%
17%

0.03 seconds
First Input Delay (FID)
81%
18%
1%

Simulate loading on mobile
86

Performance

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

Metrics

Speed Index — 2.9 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 150 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

Opportunities

Properly size images — Potential savings of 4 KiB
Images can slow down the page's load time. Ytmp3.rocks should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://ytmp4.top/template/sober/img/download.jpg
18309
4323
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ytmp3.rocks should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ytmp3.rocks should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ytmp3.rocks should consider minifying JS files.
Efficiently encode images — Potential savings of 5 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://ytmp4.top/template/sober/img/download.jpg
18309
4877
Serve images in next-gen formats — Potential savings of 11 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://ytmp4.top/template/sober/img/download.jpg
18309
11193
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 180 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://ytmp3.rocks/
180.206
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Ytmp3.rocks should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://ytmp3.rocks/
630
https://ytmp3.rocks/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ytmp3.rocks 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://ytmp3.rocks/template/sober/js/compressed.js
54
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 296 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://ytmp3.rocks/sw.js
61269
https://ytmp3.rocks/template/sober/js/compressed.js
61227
https://ytmp3.rocks/template/sober/css/app.css
53962
https://www.googletagmanager.com/gtag/js?id=UA-203090593-1
41401
https://ouwithh.club/RXVwTDA%2BVwM7bzAHHG4KZx0EOEA2T19jSTEYAH8eNxoTJ0NqBgdiWjZXXG5DKBNSdgFpVwMhRmdPUn8ecldcbkQkEi8lVGdPUnUAfEBBdRJpVwM5UhocFH4Sf1cUegR1TUJ0CWhAFnxUaEFDfAZoFEd%2FCWhAR3RSJBZJeglyTEBuTQ
21820
https://www.google-analytics.com/analytics.js
20323
https://ytmp4.top/template/sober/img/download.jpg
19230
https://ytmp3.rocks/template/sober/css/font-awesome.css
13666
https://ytmp3.rocks/
3836
https://ytmp3.rocks/template/sober/js/app.js
3703
Avoids an excessive DOM size — 95 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
95
Maximum DOM Depth
9
Maximum Child Elements
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ytmp3.rocks 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.6 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://ytmp3.rocks/
254.876
55.38
5.212
https://ytmp3.rocks/template/sober/js/compressed.js
183.88
166.848
13.932
Unattributable
129.508
56.824
0.98
https://ouwithh.club/RXVwTDA%2BVwM7bzAHHG4KZx0EOEA2T19jSTEYAH8eNxoTJ0NqBgdiWjZXXG5DKBNSdgFpVwMhRmdPUn8ecldcbkQkEi8lVGdPUnUAfEBBdRJpVwM5UhocFH4Sf1cUegR1TUJ0CWhAFnxUaEFDfAZoFEd%2FCWhAR3RSJBZJeglyTEBuTQ
112.364
100.248
6.04
https://www.google-analytics.com/analytics.js
89.992
79.036
5.376
https://ytmp3.rocks/sw.js
83.452
67.096
15.552
Minimizes main-thread work — 1.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)
Script Evaluation
559.532
Other
129.832
Style & Layout
119.336
Parse HTML & CSS
89.06
Script Parsing & Compilation
60.48
Rendering
11.32
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 — 14 requests • 296 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
14
303038
Script
6
209743
Stylesheet
2
67628
Image
1
19230
Document
1
3836
Other
4
2601
Media
0
0
Font
0
0
Third-party
7
104617
Minimize third-party usage — Third-party code blocked the main thread for 30 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)
20959
26.036
41401
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 — 5 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://ytmp3.rocks/sw.js
3060
158
https://ouwithh.club/RXVwTDA%2BVwM7bzAHHG4KZx0EOEA2T19jSTEYAH8eNxoTJ0NqBgdiWjZXXG5DKBNSdgFpVwMhRmdPUn8ecldcbkQkEi8lVGdPUnUAfEBBdRJpVwM5UhocFH4Sf1cUegR1TUJ0CWhAFnxUaEFDfAZoFEd%2FCWhAR3RSJBZJeglyTEBuTQ
4233
92
https://www.google-analytics.com/analytics.js
4148
85
https://ytmp3.rocks/template/sober/js/compressed.js
3218
57
https://ytmp3.rocks/template/sober/css/app.css
2010
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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.

Other

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://ytmp3.rocks/
http/1.1
0
39.91099994164
758
0
301
https://ytmp3.rocks/
h2
40.434999973513
219.64400005527
3836
9543
200
text/html
Document
https://ytmp3.rocks/template/sober/css/app.css
h2
234.91100000683
420.82400002982
53962
315615
200
text/css
Stylesheet
https://ytmp3.rocks/template/sober/css/font-awesome.css
h2
235.1019999478
277.24399999715
13666
58881
200
text/css
Stylesheet
https://ytmp4.top/template/sober/img/download.jpg
h2
236.73899995629
337.50599995255
19230
18309
200
image/jpeg
Image
https://www.googletagmanager.com/gtag/js?id=UA-203090593-1
h2
236.98699998204
263.96200002637
41401
102579
200
application/javascript
Script
https://ytmp3.rocks/sw.js
h2
236.22700001579
313.31700005103
61269
138522
200
application/javascript
Script
https://ytmp3.rocks/template/sober/js/compressed.js
h2
236.43399996217
304.30099996738
61227
189911
200
application/javascript
Script
https://ytmp3.rocks/template/sober/js/app.js
h2
236.57099995762
314.35500003863
3703
15886
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
446.07800000813
450.36100002471
20323
49389
200
text/javascript
Script
https://ouwithh.club/RXVwTDA%2BVwM7bzAHHG4KZx0EOEA2T19jSTEYAH8eNxoTJ0NqBgdiWjZXXG5DKBNSdgFpVwMhRmdPUn8ecldcbkQkEi8lVGdPUnUAfEBBdRJpVwM5UhocFH4Sf1cUegR1TUJ0CWhAFnxUaEFDfAZoFEd%2FCWhAR3RSJBZJeglyTEBuTQ
h2
468.16799999215
662.29600005317
21820
57189
200
application/javascript
Script
data
510.55000000633
510.61700005084
0
199
200
image/svg+xml
Image
https://www.google-analytics.com/j/collect?v=1&_v=j92&a=823749537&t=pageview&_s=1&dl=https%3A%2F%2Fytmp3.rocks%2F&ul=en-us&de=UTF-8&dt=Ytmp3%20-%20Youtube%20to%20Mp3%20Converter%20Online%20tool%20for%20Free&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=825709605&gjid=2066255605&cid=2039500953.1628100245&tid=UA-203090593-1&_gid=403304037.1628100245&_r=1&gtm=2ou820&z=188852999
h2
572.74700002745
576.02200005203
636
1
200
text/plain
XHR
https://ellenince.biz/utx?tid=909519&top=ytmp3.rocks&cb=6E1cmgtGxcBC
h2
689.54699998721
769.32600000873
1142
0
204
text/plain
XHR
https://ewledgeand.top/
h2
698.08899995405
730.70900002494
65
0
200
text/plain
XHR
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)
230.843
9.018
280.252
8.549
429.857
12.419
442.329
79.126
521.477
19.31
542.888
14.352
559.458
21.248
675.524
23.06
1498.439
7.174
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

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

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 280 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ytmp3.rocks 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://ytmp3.rocks/template/sober/css/app.css
53962
600
https://ytmp3.rocks/template/sober/css/font-awesome.css
13666
150
Reduce unused CSS — Potential savings of 65 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ytmp3.rocks 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://ytmp3.rocks/template/sober/css/app.css
53962
52824
https://ytmp3.rocks/template/sober/css/font-awesome.css
13666
13666
Reduce unused JavaScript — Potential savings of 103 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://ytmp3.rocks/template/sober/js/compressed.js
61227
42427
https://ytmp3.rocks/sw.js
61269
41223
https://www.googletagmanager.com/gtag/js?id=UA-203090593-1
41401
22010

Diagnostics

Serve static assets with an efficient cache policy — 8 resources found
Ytmp3.rocks 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://ouwithh.club/RXVwTDA%2BVwM7bzAHHG4KZx0EOEA2T19jSTEYAH8eNxoTJ0NqBgdiWjZXXG5DKBNSdgFpVwMhRmdPUn8ecldcbkQkEi8lVGdPUnUAfEBBdRJpVwM5UhocFH4Sf1cUegR1TUJ0CWhAFnxUaEFDfAZoFEd%2FCWhAR3RSJBZJeglyTEBuTQ
0
21820
https://www.google-analytics.com/analytics.js
7200000
20323
https://ytmp3.rocks/sw.js
604800000
61269
https://ytmp3.rocks/template/sober/js/compressed.js
604800000
61227
https://ytmp3.rocks/template/sober/css/app.css
604800000
53962
https://ytmp4.top/template/sober/img/download.jpg
604800000
19230
https://ytmp3.rocks/template/sober/css/font-awesome.css
604800000
13666
https://ytmp3.rocks/template/sober/js/app.js
604800000
3703

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://ytmp4.top/template/sober/img/download.jpg

Other

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

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ytmp3.rocks. 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.
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 `[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 `[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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Ytmp3.rocks 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

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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 ytmp3.rocks 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 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

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
Bootstrap
4.3.1
jQuery
3.5.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://ytmp3.rocks/template/sober/js/compressed.js
https://ytmp3.rocks/template/sober/js/_site_kit_free/assets/js/kit-free.js.map
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://ytmp3.rocks/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Requests 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.
Source

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
ReferenceError: flatpickr is not defined at HTMLDocument.<anonymous> (https://ytmp3.rocks/template/sober/js/compressed.js:22:3233) at e (https://ytmp3.rocks/template/sober/js/compressed.js:2:30005) at t (https://ytmp3.rocks/template/sober/js/compressed.js:2:30307)
86

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ytmp3.rocks. 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 ytmp3.rocks on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px
Tap targets are sized appropriately — 100% 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.

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

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.
robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
2
Sitemap: /sitemap.xml
Invalid sitemap URL

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 ytmp3.rocks. 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.
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 ytmp3.rocks on mobile screens.

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
Content is not 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.
Does not provide 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.
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.4.132
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: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 28th October, 2020
Valid To: 27th October, 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: 11898755639558054460836750437491017361
Serial Number (Hex): 08F39DF251346C8F6F7D4D3F73BE0691
Valid From: 28th October, 2025
Valid To: 27th October, 2025
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 : Oct 28 11:51:53.958 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B2:0A:0E:09:2E:4E:91:71:65:F2:D7:
4F:C0:EA:13:BB:6B:EB:61:4E:79:81:B1:35:9C:AE:07:
C8:5E:B2:60:22:02:20:28:23:F4:C5:5E:A9:D7:27:C3:
07:AD:70:CA:EB:47:05:EF:2A:DA:6F:BF:8D:60:C2:D4:
86:00:82:72:AA:F1:A6
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Oct 28 11:51:54.060 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:5D:CF:28:4E:FB:76:34:68:08:9F:D4:C4:
E4:42:CA:1B:64:0C:AE:AF:7C:3A:BC:67:13:81:B6:EC:
92:05:51:C7:02:21:00:9A:A4:B9:BC:F8:B4:F9:D3:93:
79:31:82:4B:DE:8A:CB:22:82:6C:2F:2A:71:A8:04:00:
B0:A1:ED:8D:71:E3:48
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.ytmp3.rocks
DNS:ytmp3.rocks
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 4th August, 2021
Content-Type: text/html; charset=UTF-8
expires: 19th November, 1981
cache-control: no-store, no-cache, must-revalidate
Server: cloudflare
Connection: keep-alive
set-cookie: *
pragma: no-cache
vary: User-Agent
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400
x-turbo-charged-by: LiteSpeed
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=uj2j6HHtuJ08mkGea0AOhyBCXFVffggJt4fOwGeXDJiKNGS2AdzqX3CivceEp3Bjn3zEm9APpt57JjWZTcc8s8fOKGZHohyiBVn61pbTQjBNNVtI8WCyNUbLNl%2BluQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 6799b3a9ccf8184d-EWR

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: edna.ns.cloudflare.com
venkat.ns.cloudflare.com
Full Whois:

Nameservers

Name IP Address
edna.ns.cloudflare.com 108.162.192.109
venkat.ns.cloudflare.com 172.64.35.254
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$3,865 USD 3/5
0/5
0/5
0/5

Sites hosted on the same IP address