mp3pm.com

mp3pm.com is SSL secured

Free website and domain report on mp3pm.com

Last Updated: 29th October, 2023 Update Now
Overview

Snoop Summary for mp3pm.com

This is a free and comprehensive report about mp3pm.com. Mp3pm.com is hosted in Russia on a server with an IP address of 194.1.236.159, where the local currency is RUB and Russian is the local language. Our records indicate that mp3pm.com is privately registered by Privacy Protect, LLC (PrivacyProtect.org). If mp3pm.com was to be sold it would possibly be worth $427 USD (based on the daily revenue potential of the website over a 24 month period). Mp3pm.com is somewhat popular with an estimated 200 daily unique visitors. This report was last updated 29th October, 2023.

What is mp3pm.com?

Mp3pm.com provides free MP3 and MP4 music downloads. We advise against visiting websites like mp3pm.com due to their potentially illegal/unsafe content.

About mp3pm.com

Site Preview: mp3pm.com mp3pm.com
Title: Mp3pm
Description:
Keywords and Tags: download mp3, download mp4, entertainment, free music downloads, free song downloads
Related Terms:
Fav Icon:
Age: Over 10 years old
Domain Created: 28th January, 2014
Domain Updated: 13th February, 2023
Domain Expires: 28th January, 2025
Review

Snoop Score

2/5

Valuation

$427 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,433,200
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 11
Moz Page Authority: 28

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 200
Monthly Visitors: 6,093
Yearly Visitors: 73,073
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $17 USD
Yearly Revenue: $208 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: mp3pm.com 9
Domain Name: mp3pm 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.97 seconds
Load Time Comparison: Faster than 16% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 94
Accessibility 63
Best Practices 83
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mp3.pm/
Updated: 17th January, 2023

2.34 seconds
First Contentful Paint (FCP)
62%
26%
12%

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

Simulate loading on desktop
94

Performance

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

Metrics

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

Audits

First Meaningful Paint — 0.8 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://mp3pm.com/
http/1.1
0
318.29899991862
252
0
301
text/html
https://mp3pm.com/
http/1.1
318.85199993849
867.33399983495
228
0
301
text/html
https://mp3.pm/
h2
867.69499978982
1420.8209998906
13737
95789
200
text/html
Document
https://mp3.pm/i/css/_main_min.fa31222b.css
h2
1433.9629998431
1840.5239998829
7994
39484
200
text/css
Stylesheet
https://mp3.pm/i/js/_main_min.edcc67cb.js
h2
1434.3749999534
1868.0669998284
118907
323049
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
1926.9579998218
1935.0629998371
20664
50230
200
text/javascript
Script
https://mp3.pm/i/img/bg.png
h2
1929.1049998719
2224.0309999324
4959
4684
200
image/png
Image
https://mp3.pm/i/img/spr.png
h2
1929.4719998725
2224.3969999254
36896
36620
200
image/png
Image
https://counter.yadro.ru/hit;overall?r;s800*600*24;uhttps%3A//mp3.pm/;0.5873453766732621
http/1.1
2122.3669999745
3177.2669998463
625
0
302
text/html
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=2023015451&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=IEBAAEABAAAAACAAI~&jid=1244457336&gjid=1285687036&cid=1972877917.1673993421&tid=UA-55151398-1&_gid=13354051.1673993421&_r=1&_slc=1&z=564394310
h2
2223.6279998906
2237.6029998995
605
2
200
text/plain
XHR
https://counter.yadro.ru/hit;overall?q;r;s800*600*24;uhttps%3A//mp3.pm/;0.5873453766732621
http/1.1
3177.7479997836
3835.7919999398
528
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)
1431.352
16.077
1899.686
31.874
1933.764
13.157
1950.066
15.734
1965.874
5.29
1971.568
171.251
2143.11
36.813
2179.966
49.073
2229.491
22.094
2254.426
14.104
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Mp3pm.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mp3pm.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mp3pm.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mp3pm.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mp3pm.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 18 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://mp3.pm/i/img/spr.png
36620
18395.95
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://mp3.pm/
554.119
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mp3pm.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://mp3.pm/i/img/spr.png
0
Avoids enormous network payloads — Total size was 201 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
20664
https://mp3.pm/
13737
https://mp3.pm/i/css/_main_min.fa31222b.css
7994
https://mp3.pm/i/img/bg.png
4959
https://counter.yadro.ru/hit;overall?r;s800*600*24;uhttps%3A//mp3.pm/;0.5873453766732621
625
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=2023015451&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=IEBAAEABAAAAACAAI~&jid=1244457336&gjid=1285687036&cid=1972877917.1673993421&tid=UA-55151398-1&_gid=13354051.1673993421&_r=1&_slc=1&z=564394310
605
https://counter.yadro.ru/hit;overall?q;r;s800*600*24;uhttps%3A//mp3.pm/;0.5873453766732621
528
http://mp3pm.com/
252
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. Mp3pm.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://mp3.pm/i/js/_main_min.edcc67cb.js
225.577
190.148
6.838
https://mp3.pm/
112.118
5.324
1.697
https://www.google-analytics.com/analytics.js
51.328
47.975
1.382
Minimizes main-thread work — 0.4 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
245.166
Style & Layout
55.173
Other
40.281
Rendering
30.965
Parse HTML & CSS
22.304
Script Parsing & Compilation
9.917
Garbage Collection
6.368
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 — 11 requests • 201 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
11
205395
Script
2
139571
Image
3
42383
Document
1
13737
Stylesheet
1
7994
Other
4
1710
Media
0
0
Font
0
0
Third-party
6
22902
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)
21269
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
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
842
171
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mp3pm.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Audits

Max Potential First Input Delay — 170 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 170 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mp3pm.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://mp3.pm/i/js/_main_min.edcc67cb.js
118907
120
Reduce 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
65238
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Mp3pm.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mp3pm.com/
190
https://mp3pm.com/
150
https://mp3.pm/
0
Serve static assets with an efficient cache policy — 5 resources found
Mp3pm.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20664
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

Other

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 mp3pm.com. This includes details about various page attributes that can be optimized.

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

`<html>` element has a 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"]`
Mp3pm.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
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://mp3pm.com/
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 mp3pm.com. This includes optimizations such as providing meta data.

Mobile Friendly

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

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
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.
22

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mp3pm.com 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) 64
Performance 56
Accessibility 63
Best Practices 83
SEO 87
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://mp3.pm/
Updated: 17th January, 2023

2.79 seconds
First Contentful Paint (FCP)
50%
30%
20%

0.03 seconds
First Input Delay (FID)
91%
6%
3%

Simulate loading on mobile
56

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Mp3pm.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mp3pm.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mp3pm.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mp3pm.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mp3pm.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 18 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://mp3.pm/i/img/spr.png
36620
18395.95
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 540 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/
535.909
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mp3pm.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://mp3.pm/i/img/spr.png
0
Avoids enormous network payloads — Total size was 201 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
20664
https://mp3.pm/
13720
https://mp3.pm/i/css/_main_min.fa31222b.css
7994
https://mp3.pm/i/img/bg.png
4959
https://counter.yadro.ru/hit;overall?r;s360*640*24;uhttps%3A//mp3.pm/;0.30921913402857637
626
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=2112645851&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=KEBAAEABAAAAACAAI~&jid=1161239253&gjid=17276276&cid=1160321658.1673993449&tid=UA-55151398-1&_gid=1456848768.1673993449&_r=1&_slc=1&z=726759222
605
https://counter.yadro.ru/hit;overall?q;r;s360*640*24;uhttps%3A//mp3.pm/;0.30921913402857637
528
http://mp3pm.com/
252
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. Mp3pm.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.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://mp3.pm/i/js/_main_min.edcc67cb.js
956.156
835.9
31.3
https://mp3.pm/
779.516
25.576
7.768
Unattributable
114.152
6.536
0
https://www.google-analytics.com/analytics.js
91.58
80.732
5.528
Minimizes main-thread work — 2.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
948.744
Style & Layout
443.152
Other
221.024
Rendering
207.396
Parse HTML & CSS
89.448
Script Parsing & Compilation
44.596
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 — 11 requests • 201 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
11
205379
Script
2
139571
Image
3
42383
Document
1
13720
Stylesheet
1
7994
Other
4
1711
Media
0
0
Font
0
0
Third-party
6
22903
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)
21269
28.984
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
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 — 8 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
3405
690
https://mp3.pm/i/js/_main_min.edcc67cb.js
3240
165
https://mp3.pm/
2044
117
https://mp3.pm/i/js/_main_min.edcc67cb.js
4095
96
https://mp3.pm/i/js/_main_min.edcc67cb.js
4191
92
https://www.google-analytics.com/analytics.js
2820
87
https://mp3.pm/
1890
69
https://mp3.pm/
1959
54
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mp3pm.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://mp3pm.com/
http/1.1
0
279.48600007221
252
0
301
text/html
https://mp3pm.com/
http/1.1
280.12600005604
755.12900017202
228
0
301
text/html
https://mp3.pm/
h2
755.51500008442
1290.8030000981
13720
95789
200
text/html
Document
https://mp3.pm/i/css/_main_min.fa31222b.css
h2
1307.0520001929
1716.2240000907
7994
39484
200
text/css
Stylesheet
https://mp3.pm/i/js/_main_min.edcc67cb.js
h2
1307.2310001589
2131.3550001942
118907
323049
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
h2
2208.3930000663
2213.7070000172
20664
50230
200
text/javascript
Script
https://mp3.pm/i/img/bg.png
h2
2210.9720001463
2342.4080000259
4959
4684
200
image/png
Image
https://mp3.pm/i/img/spr.png
h2
2211.5220001433
2587.6500001177
36896
36620
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=2112645851&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=KEBAAEABAAAAACAAI~&jid=1161239253&gjid=17276276&cid=1160321658.1673993449&tid=UA-55151398-1&_gid=1456848768.1673993449&_r=1&_slc=1&z=726759222
h2
2397.7290000767
2401.5540000983
605
2
200
text/plain
XHR
https://counter.yadro.ru/hit;overall?r;s360*640*24;uhttps%3A//mp3.pm/;0.30921913402857637
http/1.1
2500.0040000305
3495.3630000819
626
0
302
text/html
https://counter.yadro.ru/hit;overall?q;r;s360*640*24;uhttps%3A//mp3.pm/;0.30921913402857637
http/1.1
3496.4310000651
4493.4580000117
528
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)
1295.023
17.307
2159.422
5.632
2165.071
41.271
2209.831
27.194
2239.23
15.596
2257.029
6.744
2263.829
58.55
2322.4
21.645
2344.123
172.467
2516.8
48.24
2568.296
23.061
2596.281
6.404
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.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.3 s
The time taken for the page to become fully interactive.
Speed Index — 5.1 s
The time taken for the page contents to be visibly populated.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 790 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mp3pm.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://mp3.pm/i/css/_main_min.fa31222b.css
7994
150
https://mp3.pm/i/js/_main_min.edcc67cb.js
118907
600
Reduce 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
65238
Serve static assets with an efficient cache policy — 5 resources found
Mp3pm.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20664
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

Metrics

Total Blocking Time — 880 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).
Largest Contentful Paint — 4.1 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 690 ms
Users could experience a delay when interacting with the page.

Other

Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Mp3pm.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://mp3pm.com/
630
https://mp3pm.com/
480
https://mp3.pm/
0
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
First Contentful Paint (3G) — 5655 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
63

Accessibility

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

Navigation

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

ARIA

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

Names and labels

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

Tables and lists

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

Internationalization and localization

`<html>` element has a 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"]`
Mp3pm.com 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.
83

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
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://mp3pm.com/
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 mp3pm.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mp3pm.com on mobile screens.
Document uses legible font sizes — 80.46% 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
8.87%
10px
ul.mp3list > li em
2.63%
11px
footer#footer
2.29%
11px
h5#fixplayer-progress_bar-title > em, span#fixplayer-progress_bar-now > em
0.56%
11px
5.19%
< 12px
80.46%
≥ 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
25x11
27x11
66x11
25x11
35x11
38x11
31x11
70x11
36x11
50x11
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
209x18
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
209x18
30x11
50x11
48x11
50x11
25x11
42x11
30x11
25x11
25x11
36x11
38x11
27x11
35x11
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.
30

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mp3pm.com 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: 194.1.236.159
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: Yes
Name: Domain Admin
Organization: Privacy Protect, LLC (PrivacyProtect.org)
Country: US
City: Burlington
State: MA
Post Code: 01803
Email: contact@privacyprotect.org
Phone: +1.8022274003
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
PDR Ltd. d/b/a PublicDomainRegistry.com 104.16.180.120
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: mp3pm.com
Issued By: R3
Valid From: 2nd April, 2022
Valid To: 1st July, 2022
Subject: CN = mp3pm.com
Hash: 64323d8e
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x039C7037EC2626D41C3CD6E2F691BF7B192B
Serial Number (Hex): 039C7037EC2626D41C3CD6E2F691BF7B192B
Valid From: 2nd April, 2024
Valid To: 1st 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 : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Apr 2 19:46:02.183 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:8B:43:06:00:BF:E5:16:24:BF:34:05:
33:B7:12:3B:9A:C6:98:D5:84:03:4E:1E:25:FB:EF:B0:
FA:31:1F:24:6A:02:21:00:FB:8F:17:C0:D6:23:88:F5:
77:32:94:8F:DD:5B:DB:59:42:F5:68:BF:C8:5C:96:3B:
F0:A7:77:E6:FD:17:8B:6B
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Apr 2 19:46:02.223 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:A1:F2:0D:D2:99:2A:E6:2D:99:17:AF:
84:7D:6D:B8:A3:FF:A2:B2:15:DC:3E:22:A5:4E:89:2E:
28:4A:7C:A1:10:02:21:00:EB:F4:5C:94:78:DF:76:50:
2F:10:2A:2D:41:A2:A0:12:EA:02:19:EA:40:3D:29:63:
E4:D1:B4:76:62:01:83:0E
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mp3-pm.com
DNS:mp3-pm.info
DNS:mp3-pm.org
DNS:mp3pm.com
DNS:www.mp3-pm.biz
DNS:www.mp3-pm.com
DNS:www.mp3-pm.info
DNS:www.mp3-pm.org
DNS:www.mp3pm.com
DNS:mp3-pm.biz
Technical

DNS Lookup

A Records

Host IP Address Class TTL
mp3pm.com. 194.1.236.159 IN 3600

NS Records

Host Nameserver Class TTL
mp3pm.com. pns6.cloudns.net. IN 3600
mp3pm.com. pns10.cloudns.net. IN 3600
mp3pm.com. pns3.cloudns.net. IN 3600
mp3pm.com. pns8.cloudns.net. IN 3600
mp3pm.com. pns4.cloudns.net. IN 3600
mp3pm.com. pns9.cloudns.net. IN 3600
mp3pm.com. pns1.cloudns.net. IN 3600
mp3pm.com. pns2.cloudns.net. IN 3600
mp3pm.com. pns5.cloudns.net. IN 3600
mp3pm.com. pns7.cloudns.net. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
mp3pm.com. ns1.cloudns.net. support.cloudns.net. 3600

TXT Records

Host Value Class TTL
mp3pm.com. yandex-verification: IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 404 Not Found
Server: nginx
Date: 5th March, 2023
Content-Type: text/html; charset=UTF-8
Content-Length: 548
Connection: keep-alive

Whois Lookup

Created: 28th January, 2014
Changed: 13th February, 2023
Expires: 28th January, 2025
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Status: clientTransferProhibited
Nameservers: pns1.cloudns.net
pns2.cloudns.net
pns3.cloudns.net
pns4.cloudns.net
pns5.cloudns.net
pns6.cloudns.net
pns7.cloudns.net
pns8.cloudns.net
pns9.cloudns.net
Owner Name: Domain Admin
Owner Organization: Privacy Protect, LLC (PrivacyProtect.org)
Owner Street: 10 Corporate Drive
Owner Post Code: 01803
Owner City: Burlington
Owner State: MA
Owner Country: US
Owner Phone: +1.8022274003
Owner Email: contact@privacyprotect.org
Admin Name: Domain Admin
Admin Organization: Privacy Protect, LLC (PrivacyProtect.org)
Admin Street: 10 Corporate Drive
Admin Post Code: 01803
Admin City: Burlington
Admin State: MA
Admin Country: US
Admin Phone: +1.8022274003
Admin Email: contact@privacyprotect.org
Tech Name: Domain Admin
Tech Organization: Privacy Protect, LLC (PrivacyProtect.org)
Tech Street: 10 Corporate Drive
Tech Post Code: 01803
Tech City: Burlington
Tech State: MA
Tech Country: US
Tech Phone: +1.8022274003
Tech Email: contact@privacyprotect.org
Full Whois: Domain Name: MP3PM.COM
Registry Domain ID: 1844573832_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2023-02-13T20:30:14Z
Creation Date: 2014-01-28T19:18:44Z
Registrar Registration Expiration Date: 2025-01-28T19:18:44Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Domain Admin
Registrant Organization: Privacy Protect, LLC (PrivacyProtect.org)
Registrant Street: 10 Corporate Drive
Registrant City: Burlington
Registrant State/Province: MA
Registrant Postal Code: 01803
Registrant Country: US
Registrant Phone: +1.8022274003
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: contact@privacyprotect.org
Registry Admin ID: Not Available From Registry
Admin Name: Domain Admin
Admin Organization: Privacy Protect, LLC (PrivacyProtect.org)
Admin Street: 10 Corporate Drive
Admin City: Burlington
Admin State/Province: MA
Admin Postal Code: 01803
Admin Country: US
Admin Phone: +1.8022274003
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: contact@privacyprotect.org
Registry Tech ID: Not Available From Registry
Tech Name: Domain Admin
Tech Organization: Privacy Protect, LLC (PrivacyProtect.org)
Tech Street: 10 Corporate Drive
Tech City: Burlington
Tech State/Province: MA
Tech Postal Code: 01803
Tech Country: US
Tech Phone: +1.8022274003
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: contact@privacyprotect.org
Name Server: pns1.cloudns.net
Name Server: pns2.cloudns.net
Name Server: pns3.cloudns.net
Name Server: pns4.cloudns.net
Name Server: pns5.cloudns.net
Name Server: pns6.cloudns.net
Name Server: pns7.cloudns.net
Name Server: pns8.cloudns.net
Name Server: pns9.cloudns.net
DNSSEC: Unsigned
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-05T15:50:16Z <<<

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

Registration Service Provided By: REGWAY.COM

PRIVACYPROTECT.ORG is providing privacy protection services to this domain name to
protect the owner from spam and phishing attacks. PrivacyProtect.org is not
responsible for any of the activities associated with this domain name. If you wish
to report any abuse concerning the usage of this domain name, you may do so at
http://privacyprotect.org/contact. We have a stringent abuse policy and any
complaint will be actioned within a short period of time.

The data in this whois database is provided to you for information purposes
only, that is, to assist you in obtaining information about or related to a
domain name registration record. We make this information available "as is",
and do not guarantee its accuracy. By submitting a whois query, you agree
that you will use this data only for lawful purposes and that, under no
circumstances will you use this data to:
(1) enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or
by telephone.
The compilation, repackaging, dissemination or other use of this data is
expressly prohibited without prior written consent from us. The Registrar of
record is PDR Ltd. d/b/a PublicDomainRegistry.com.
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.


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
pns5.cloudns.net 185.136.96.111
pns6.cloudns.net 185.136.97.111
pns7.cloudns.net 185.136.98.111
pns8.cloudns.net 185.136.99.111
pns9.cloudns.net 185.136.96.111
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$2,382 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5