mp3.pm

mp3.pm is SSL secured

Free website and domain report on mp3.pm

Last Updated: 1st April, 2023 Update Now
Overview

Snoop Summary for mp3.pm

This is a free and comprehensive report about mp3.pm. Mp3.pm is hosted in Russia on a server with an IP address of 185.248.101.126, where the local currency is RUB and Russian is the local language. Mp3.pm has the potential to be earning an estimated $5 USD per day from advertising revenue. If mp3.pm was to be sold it would possibly be worth $3,429 USD (based on the daily revenue potential of the website over a 24 month period). Mp3.pm is quite popular with an estimated 1,644 daily unique visitors. This report was last updated 1st April, 2023.

About mp3.pm

Site Preview: mp3.pm mp3.pm
Title: Most popular songs - download free mp3 - mp3.pm
Description: Dua Lipa - Lost In Your Light (feat. Miguel) Paul Damixie - Get Lost( Matt Nash - Know My Love Paramore - Hard Times TCTS feat Sage The Gemini & Kelis - Do It Like Me (Icy Feet) Filatov & Ka 1d9
Keywords and Tags: potential illegal software
Related Terms: dua, dua after adhan, dua of musa, gemini, hp dua, lost love back, lost on campus uq, mangga dua, miguel almiron, taraweeh dua
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$3,429 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 479,706
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: 1,644
Monthly Visitors: 50,024
Yearly Visitors: 599,895
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $143 USD
Yearly Revenue: $1,710 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: mp3.pm 6
Domain Name: mp3 3
Extension (TLD): pm 2

Page Speed Analysis

Average Load Time: 0.75 seconds
Load Time Comparison: Faster than 88% of sites

PageSpeed Insights

Avg. (All Categories) 74
Performance 96
Accessibility 63
Best Practices 87
SEO 90
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mp3.pm/
Updated: 10th April, 2021

3.20 seconds
First Contentful Paint (FCP)
16%
55%
29%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
96

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.7 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mp3.pm as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mp3.pm/
http/1.1
0
299.9500001315
249
0
301
text/html
https://mp3.pm/
h2
300.62100011855
885.96300012432
13956
95930
200
text/html
Document
https://mp3.pm/i/css/_main_min.fa31222b.css
h2
903.43099995516
1111.198999919
7994
39484
200
text/css
Stylesheet
https://mp3.pm/i/js/_main_min.edcc67cb.js
h2
903.68600003421
1743.1290000677
118907
323049
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1797.3740000743
1800.7920000236
20093
48759
200
text/javascript
Script
https://counter.yadro.ru/hit;overall?r;s800*600*24;uhttps%3A//mp3.pm/;0.9079742424334474
http/1.1
1899.4680000469
2578.4370000474
562
0
302
text/html
https://mp3.pm/i/img/bg.png
h2
1903.0170000624
2118.0980000645
4959
4684
200
image/png
Image
https://mp3.pm/i/img/spr.png
h2
1903.226000024
2457.9219999723
36896
36620
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=1782239233&t=pageview&_s=1&dl=https%3A%2F%2Fmp3.pm%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Most%20popular%20songs%20-%20download%20free%20mp3%20-%20mp3.pm&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=698018953&gjid=1294167836&cid=1741219227.1618082917&tid=UA-55151398-1&_gid=220986531.1618082917&_r=1&_slc=1&z=436598022
h2
1993.6430000234
1996.5460000094
610
2
200
text/plain
XHR
https://counter.yadro.ru/hit;overall?q;r;s800*600*24;uhttps%3A//mp3.pm/;0.9079742424334474
http/1.1
2578.7370000035
3256.3120000996
496
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
916.842
8.533
1791.497
150.012
1941.525
36.629
1979.636
19.724
2002.698
19.353
2487.275
7.263
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Mp3.pm should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mp3.pm should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mp3.pm should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mp3.pm should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mp3.pm should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 64 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://mp3.pm/i/js/_main_min.edcc67cb.js
118907
65372
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 13 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://mp3.pm/i/img/spr.png
36620
12806
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 590 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://mp3.pm/
586.338
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Mp3.pm should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mp3.pm/
190
https://mp3.pm/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mp3.pm should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://mp3.pm/i/img/spr.png
0

Diagnostics

Avoids enormous network payloads — Total size was 200 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mp3.pm/i/js/_main_min.edcc67cb.js
118907
https://mp3.pm/i/img/spr.png
36896
https://www.google-analytics.com/analytics.js
20093
https://mp3.pm/
13956
https://mp3.pm/i/css/_main_min.fa31222b.css
7994
https://mp3.pm/i/img/bg.png
4959
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=1782239233&t=pageview&_s=1&dl=https%3A%2F%2Fmp3.pm%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Most%20popular%20songs%20-%20download%20free%20mp3%20-%20mp3.pm&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=698018953&gjid=1294167836&cid=1741219227.1618082917&tid=UA-55151398-1&_gid=220986531.1618082917&_r=1&_slc=1&z=436598022
610
https://counter.yadro.ru/hit;overall?r;s800*600*24;uhttps%3A//mp3.pm/;0.9079742424334474
562
https://counter.yadro.ru/hit;overall?q;r;s800*600*24;uhttps%3A//mp3.pm/;0.9079742424334474
496
http://mp3.pm/
249
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mp3.pm 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://mp3.pm/i/js/_main_min.edcc67cb.js
163.074
131.441
6.46
https://mp3.pm/
71.676
3.714
1.251
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
154.409
Other
33.058
Style & Layout
32.363
Rendering
26.414
Parse HTML & CSS
19.448
Script Parsing & Compilation
9.123
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 — 10 requests • 200 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
10
204722
Script
2
139000
Image
3
42351
Document
1
13956
Stylesheet
1
7994
Other
3
1421
Media
0
0
Font
0
0
Third-party
4
21761
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)
20703
0
1058
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.
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 — 1 long task 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://mp3.pm/i/js/_main_min.edcc67cb.js
500
150
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Metrics

Speed Index — 1.5 s
The time taken for the page contents to be visibly populated.

Opportunities

Eliminate render-blocking resources — Potential savings of 330 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mp3.pm 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://mp3.pm/i/js/_main_min.edcc67cb.js
118907
120

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Mp3.pm 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://www.google-analytics.com/analytics.js
7200000
20093
https://mp3.pm/i/js/_main_min.edcc67cb.js
604800000
118907
https://mp3.pm/i/img/spr.png
604800000
36896
https://mp3.pm/i/css/_main_min.fa31222b.css
604800000
7994
https://mp3.pm/i/img/bg.png
604800000
4959
Avoid an excessive DOM size — 842 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
842
Maximum DOM Depth
9
Maximum Child Elements
50

Diagnostics

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
63

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mp3.pm. 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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

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

Internationalization and localization

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

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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
jQuery
2.1.1
AngularJS
1.3.0-rc.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.
URL Map URL
https://mp3.pm/i/js/_main_min.edcc67cb.js
https://mp3.pm/i/js/angular-animate.min.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://mp3.pm/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
1
Medium
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mp3.pm. 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 mp3.pm 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.
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.

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.
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 mp3.pm. 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 mp3.pm 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 87
Accessibility 63
Best Practices 87
SEO 87
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mp3.pm/
Updated: 10th April, 2021

3.91 seconds
First Contentful Paint (FCP)
7%
50%
43%

0.02 seconds
First Input Delay (FID)
96%
3%
1%

Simulate loading on mobile
87

Performance

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

Metrics

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

Other

First CPU Idle — 3.5 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive mp3.pm as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mp3.pm/
http/1.1
0
270.59900015593
249
0
301
text/html
https://mp3.pm/
h2
271.22600004077
432.17899999581
13956
95930
200
text/html
Document
https://mp3.pm/i/css/_main_min.fa31222b.css
h2
448.34699993953
595.58700001799
7994
39484
200
text/css
Stylesheet
https://mp3.pm/i/js/_main_min.edcc67cb.js
h2
448.63700005226
867.97100002877
118907
323049
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
917.03999997117
921.459000092
20093
48759
200
text/javascript
Script
https://counter.yadro.ru/hit;overall?r;s360*640*24;uhttps%3A//mp3.pm/;0.47312825594297325
http/1.1
1024.9570000451
1705.7730001397
563
0
302
text/html
https://mp3.pm/i/img/bg.png
h2
1028.1940000132
1247.7700000163
4959
4684
200
image/png
Image
https://mp3.pm/i/img/spr.png
h2
1028.5249999724
1173.0969999917
36896
36620
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=486973815&t=pageview&_s=1&dl=https%3A%2F%2Fmp3.pm%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Most%20popular%20songs%20-%20download%20free%20mp3%20-%20mp3.pm&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=801622386&gjid=1303071742&cid=765612274.1618082935&tid=UA-55151398-1&_gid=191729341.1618082935&_r=1&_slc=1&z=828407174
h2
1115.45199994
1119.144000113
610
2
200
text/plain
XHR
https://counter.yadro.ru/hit;overall?q;r;s360*640*24;uhttps%3A//mp3.pm/;0.47312825594297325
http/1.1
1706.0210001655
2384.2319999821
496
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
464.018
7.743
914.726
154.589
1069.339
36.064
1106.792
17.535
1127.476
17.394
1203.631
7.967
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Mp3.pm should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mp3.pm should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mp3.pm should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mp3.pm should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mp3.pm should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 13 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://mp3.pm/i/img/spr.png
36620
12806
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 160 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://mp3.pm/
161.95
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Mp3.pm should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mp3.pm/
630
https://mp3.pm/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mp3.pm should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://mp3.pm/i/img/spr.png
0

Diagnostics

Avoids enormous network payloads — Total size was 200 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://mp3.pm/i/js/_main_min.edcc67cb.js
118907
https://mp3.pm/i/img/spr.png
36896
https://www.google-analytics.com/analytics.js
20093
https://mp3.pm/
13956
https://mp3.pm/i/css/_main_min.fa31222b.css
7994
https://mp3.pm/i/img/bg.png
4959
https://www.google-analytics.com/j/collect?v=1&_v=j89&a=486973815&t=pageview&_s=1&dl=https%3A%2F%2Fmp3.pm%2F&dp=%2F&ul=en-us&de=UTF-8&dt=Most%20popular%20songs%20-%20download%20free%20mp3%20-%20mp3.pm&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=801622386&gjid=1303071742&cid=765612274.1618082935&tid=UA-55151398-1&_gid=191729341.1618082935&_r=1&_slc=1&z=828407174
610
https://counter.yadro.ru/hit;overall?r;s360*640*24;uhttps%3A//mp3.pm/;0.47312825594297325
563
https://counter.yadro.ru/hit;overall?q;r;s360*640*24;uhttps%3A//mp3.pm/;0.47312825594297325
496
http://mp3.pm/
249
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mp3.pm 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://mp3.pm/i/js/_main_min.edcc67cb.js
645.28
518.412
23.452
https://mp3.pm/
287.38
13.4
4.988
https://www.google-analytics.com/analytics.js
74.496
64.56
4.972
Unattributable
67.488
3.148
0.536
Minimizes main-thread work — 1.1 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
599.52
Style & Layout
148.364
Other
121.648
Rendering
86.328
Parse HTML & CSS
78.264
Script Parsing & Compilation
33.948
Garbage Collection
15.516
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 — 10 requests • 200 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
10
204723
Script
2
139000
Image
3
42351
Document
1
13956
Stylesheet
1
7994
Other
3
1422
Media
0
0
Font
0
0
Third-party
4
21762
Minimize third-party usage — Third-party code blocked the main thread for 10 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)
20703
12.072
1059
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.
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 — 4 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://mp3.pm/i/js/_main_min.edcc67cb.js
1860
618
https://mp3.pm/i/js/_main_min.edcc67cb.js
2478
72
https://mp3.pm/i/js/_main_min.edcc67cb.js
2550
70
https://www.google-analytics.com/analytics.js
3408
70
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

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

Metrics

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

Other

First Meaningful Paint — 2.6 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 4650 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused JavaScript — Potential savings of 64 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://mp3.pm/i/js/_main_min.edcc67cb.js
118907
65372

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Mp3.pm 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://www.google-analytics.com/analytics.js
7200000
20093
https://mp3.pm/i/js/_main_min.edcc67cb.js
604800000
118907
https://mp3.pm/i/img/spr.png
604800000
36896
https://mp3.pm/i/css/_main_min.fa31222b.css
604800000
7994
https://mp3.pm/i/img/bg.png
604800000
4959
Avoid an excessive DOM size — 842 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
842
Maximum DOM Depth
9
Maximum Child Elements
50

Opportunities

Eliminate render-blocking resources — Potential savings of 1,430 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mp3.pm 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://mp3.pm/i/css/_main_min.fa31222b.css
7994
150
https://mp3.pm/i/js/_main_min.edcc67cb.js
118907
600

Diagnostics

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
63

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mp3.pm. 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.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

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

Contrast

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

Internationalization and localization

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

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
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
jQuery
2.1.1
AngularJS
1.3.0-rc.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.
URL Map URL
https://mp3.pm/i/js/_main_min.edcc67cb.js
https://mp3.pm/i/js/angular-animate.min.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://mp3.pm/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
1
Medium
87

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for mp3.pm. 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 mp3.pm on mobile screens.
Document uses legible font sizes — 78.09% 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
footer#footer ul#foo-tags > li
11.40%
10px
ul.mp3list > li em
2.58%
11px
footer#footer
2.25%
11px
h5#fixplayer-progress_bar-title > em, span#fixplayer-progress_bar-now > em
0.55%
11px
5.13%
< 12px
78.09%
≥ 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.
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.
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.

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.

Mobile Friendly

Tap targets are not sized appropriately — 47% 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
26x11
13x11
13x11
24x11
63x11
24x11
30x11
63x11
30x11
42x11
73x11
26x11
78x11
125x11
68x11
81x11
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
a
209x18
209x18
209x18
209x18
209x18
209x18
209x18
(
209x18
209x18
209x18
209x18
Sia
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
Sia
209x18
209x18
209x18
LP
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
77x11
73x11
60x11
26x11
42x11
67x11
68x11
73x11
32x28

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

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 mp3.pm. 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 mp3.pm 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.
Hosting

Server Location

Server IP Address: 185.248.101.126
Continent: Europe
Country: Russia
Russia Flag
Region:
City:
Longitude: 37.6068
Latitude: 55.7386
Currencies: RUB
Languages: Russian

Web Hosting Provider

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: 3/5
WOT Trustworthiness: 60/100
WOT Child Safety: 51/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: mp3.pm
Issued By: R3
Valid From: 7th April, 2021
Valid To: 6th July, 2021
Subject: CN = mp3.pm
Hash: 7b60dbf0
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03009C9B155C350F14B9E974B60D2AFA33D4
Serial Number (Hex): 03009C9B155C350F14B9E974B60D2AFA33D4
Valid From: 7th April, 2024
Valid To: 6th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

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 : Apr 7 04:45:31.916 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EB:48:0C:28:FF:A1:95:D1:50:32:FA:
4D:DB:BE:9A:06:26:E6:48:7E:8F:AC:4A:D2:A1:11:BD:
8A:3B:44:EF:08:02:21:00:F8:44:46:36:C7:F7:6F:81:
FB:7F:25:6E:11:74:63:76:88:F0:28:2D:DE:EE:BB:01:
22:B5:22:B9:F5:BB:8C:E0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Apr 7 04:45:32.090 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:7A:59:00:C2:5C:39:25:33:64:0F:E9:EB:
13:B5:38:13:EE:60:58:41:9F:69:FF:99:FF:C6:54:3B:
C4:07:C4:08:02:20:33:E8:7E:17:C9:B7:47:4A:09:AD:
31:4D:EA:49:E4:C3:85:79:D2:4A:02:67:A5:39:D5:B1:
B2:DF:D3:0D:01:0E
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mp3.pm
DNS:*.mp3.pm
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mp3.pm. 185.248.101.126 IN 299

NS Records

Host Nameserver Class TTL
mp3.pm. pns1.cloudns.net. IN 3599
mp3.pm. pns3.cloudns.net. IN 3599
mp3.pm. pns4.cloudns.net. IN 3599
mp3.pm. pns2.cloudns.net. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
mp3.pm. ns1.cloudns.net. support.cloudns.net. 3599

TXT Records

Host Value Class TTL
mp3.pm. yandex-verification: IN 3599
mp3.pm. yandex-verification: IN 3599
mp3.pm. google-site-verification=j6zNWdOWJOHNkHG89mnb1HJa0mTU5qcjL6vPudaaA5M IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 10th April, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: pns1.cloudns.net
pns2.cloudns.net
pns3.cloudns.net
pns4.cloudns.net
Full Whois: %%
%% This is the AFNIC Whois server.
%%
%% complete date format : YYYY-MM-DDThh:mm:ssZ
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See https://www.afnic.fr/en/products-and-services/services/whois/whois-special-notice/
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [67.205.137.127 REQUEST] >> mp3.pm
%%
%% RL Net [##########] - RL IP [########..]
%%

domain: mp3.pm
status: ACTIVE
hold: NO
holder-c: ANO00-FRNIC
admin-c: ANO00-FRNIC
tech-c: DA55158-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL43976-FRNIC
registrar: TLD Registrar Solutions Ltd
Expiry Date: 2025-05-27T19:33:30Z
created: 2013-01-05T16:11:45Z
last-update: 2019-06-21T06:43:30Z
source: FRNIC

ns-list: NSL43976-FRNIC
nserver: pns1.cloudns.net
nserver: pns2.cloudns.net
nserver: pns3.cloudns.net
nserver: pns4.cloudns.net
nserver: pns5.cloudns.net
nserver: pns6.cloudns.net
nserver: pns7.cloudns.net
nserver: pns8.cloudns.net
source: FRNIC

registrar: TLD Registrar Solutions Ltd
type: Isp Option 1
address: 35-39 Moorgate
address: Level 1
address: EC2R 6AR LONDON
country: GB
phone: +44 2034357304
e-mail: admin@tldregistrarsolutions.com
website: https://internetbs.net/en/domain-name-registrations/price.html?setCurrency=EUR
anonymous: NO
registered: 2014-11-17T12:00:00Z
source: FRNIC

nic-hdl: ANO00-FRNIC
type: PERSON
contact: Ano Nymous
remarks: -------------- WARNING --------------
remarks: While the registrar knows him/her,
remarks: this person chose to restrict access
remarks: to his/her personal data. So PLEASE,
remarks: don't send emails to Ano Nymous. This
remarks: address is bogus and there is no hope
remarks: of a reply.
remarks: -------------- WARNING --------------
registrar: TLD Registrar Solutions Ltd
changed: 2015-11-26T13:58:23Z anonymous@anonymous
anonymous: YES
obsoleted: NO
eligstatus: ok
eligsource: REGISTRY
eligdate: 2015-11-26T13:58:22Z
reachmedia: email
reachstatus: ok
reachsource: REGISTRY
reachdate: 2015-11-26T13:58:22Z
source: FRNIC

nic-hdl: ANO00-FRNIC
type: PERSON
contact: Ano Nymous
remarks: -------------- WARNING --------------
remarks: While the registrar knows him/her,
remarks: this person chose to restrict access
remarks: to his/her personal data. So PLEASE,
remarks: don't send emails to Ano Nymous. This
remarks: address is bogus and there is no hope
remarks: of a reply.
remarks: -------------- WARNING --------------
registrar: TLD Registrar Solutions Ltd
changed: 2015-11-26T13:58:23Z anonymous@anonymous
anonymous: YES
obsoleted: NO
eligstatus: ok
eligsource: REGISTRY
eligdate: 2015-11-26T13:58:22Z
reachmedia: email
reachstatus: ok
reachsource: REGISTRY
reachdate: 2015-11-26T13:58:22Z
source: FRNIC

nic-hdl: DA55158-FRNIC
type: PERSON
contact: Domain Admin
address: TLD Registrar Solutions Ltd
address: Lvl 1, 35-39 Moorgate
address: EC2R 6AR London
country: GB
phone: +44.2034357312
fax-no: +44.2033880601
e-mail: admin@tldregistrarsolutions.com
registrar: TLD Registrar Solutions Ltd
changed: 2019-06-19T16:32:56Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC

Nameservers

Name IP Address
pns1.cloudns.net 185.136.96.111
pns2.cloudns.net 185.136.97.111
pns3.cloudns.net 185.136.98.111
pns4.cloudns.net 185.136.99.111
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$7,124 USD 3/5
$1,015 USD 1/5
$310 USD 1/5
$1,049 USD

Sites hosted on the same IP address