landr.com Website Information

Daily Unique Visits: 69,613

Daily Page Views: 417,678

Income Per Day: $835

Estimated Value: $601,200

landr.com is registered under .COM top-level domain. Please check other sites in .COM zone.

No name server records were found.

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website landr.com position in Alexa rank database was 20376 and the lowest rank position was 24607. Current position of landr.com in Alexa rank database is 20603.

Desktop speed score of landr.com (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of landr.com (67/100) is better than the results of 18.73% of other sites and means that the page is not mobile-friendly.

Mobile speed score of landr.com (52/100) is better than the results of 37.6% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

landr.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

landr.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain Name: LANDR.COM
Registry Domain ID: 69075413_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com
Updated Date: 2024-03-07T00:27:25Z
Creation Date: 2001-04-10T14:05:06Z
Registry Expiry Date: 2025-04-10T14:05:06Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: trustandsafety@support.aws.com
Registrar Abuse Contact Phone: +1.2024422253
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS-1415.AWSDNS-48.ORG
Name Server: NS-1859.AWSDNS-40.CO.UK
Name Server: NS-51.AWSDNS-06.COM
Name Server: NS-710.AWSDNS-24.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-20T19:41:01Z

landr.com server information

Servers Location

landr.com desktop page speed rank

Last tested: 2016-11-19

Desktop Speed Medium

80/100

landr.com Desktop Speed Test Quick Summary

priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.landr.com/js/app.min.js?v=2.18.1
https://cdn.optimizely.com/js/2519221268.js

Optimize CSS Delivery of the following:

https://www.landr.com/css/app.css?v=2.18.1

priority - 6Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 1Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 8.1KiB (84% reduction).

Compressing https://www.landr.com/api/v1/config/programs?count…4946-b696-f4bd84f00a96 could save 8.1KiB (84% reduction).

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 8KiB (35% reduction).

Compressing https://www.landr.com/img/partners/music_radar.png?version=2.18.1 could save 2.3KiB (52% reduction).
Compressing https://www.landr.com/img/partners/vice.png?version=2.18.1 could save 2.1KiB (53% reduction).
Compressing https://www.landr.com/img/partners/fast_company.png?version=2.18.1 could save 1.5KiB (22% reduction).
Compressing https://www.landr.com/img/logo-landr.png could save 1.2KiB (29% reduction).
Compressing https://www.landr.com/img/partners/turbo.png?version=2.18.1 could save 904B (23% reduction).

landr.com Desktop Resource Breakdown

Total Resources	99
Number of Hosts	34
Static Resources	18
JavaScript Resources	17
CSS Resources	1

landr.com mobile page speed rank

Last tested: 2017-06-03

Mobile Speed Bad

52/100

landr.com Mobile Speed Test Quick Summary

priority - 56Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.landr.com/js/app.min.js?v=2.36.0

Optimize CSS Delivery of the following:

https://www.landr.com/css/app.css?v=2.36.0

priority - 19Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 186.6KiB (44% reduction).

Compressing https://www.landr.com/img/backgrounds/landr-hero-v3.jpg?v1 could save 102.9KiB (51% reduction).
Compressing https://www.landr.com/img/backgrounds/ab-electro.jpg could save 77.7KiB (39% reduction).
Compressing https://www.landr.com/img/partners/fast_company.png?version=2.36.0 could save 1.5KiB (22% reduction).
Compressing https://www.landr.com/img/partners/music_radar.png?version=2.36.0 could save 1.3KiB (30% reduction).
Compressing https://www.landr.com/img/partners/vice.png?version=2.36.0 could save 1.2KiB (31% reduction).
Compressing https://www.landr.com/img/logo-landr.png could save 1.1KiB (25% reduction).
Compressing https://www.landr.com/img/partners/turbo.png?version=2.36.0 could save 920B (24% reduction).

priority - 14Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://nexus-websocket-a.intercom.io/client-test (expiration not specified)
https://nexus-websocket-b.intercom.io/client-test (expiration not specified)
https://www.landr.com/i18n/angular-locale_en-us.js (expiration not specified)
https://www.landr.com/img/backgrounds/ab-electro.jpg (expiration not specified)
https://www.landr.com/img/backgrounds/ab-indie.jpg (expiration not specified)
https://www.landr.com/img/backgrounds/ab-rnb.jpg (expiration not specified)
https://www.landr.com/img/backgrounds/ab-songwriter.jpg (expiration not specified)
https://www.landr.com/img/logo-landr-mini.png (expiration not specified)
https://www.landr.com/img/logo-landr-vintage@3x.png (expiration not specified)
https://www.landr.com/img/logo-landr-white.png (expiration not specified)
https://www.landr.com/img/logo-landr.png (expiration not specified)
https://www.landr.com/img/svg/icon-pointer-30.svg (expiration not specified)
https://cdn.optimizely.com/js/2519221268.js (2.1 minutes)
https://s.adroll.com/j/roundtrip.js (5 minutes)
https://s.adroll.com/pixel/W2GJ334XQFAOZH5MXFWDBH/…E2ALZUZFWZN4ZWIL7JQ.js (5 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1551588871778054?v=2.7.12 (20 minutes)
https://connect.facebook.net/signals/config/294658584065027?v=2.7.12 (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 2Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 14.5KiB (86% reduction).

Compressing https://www.landr.com/api/v1/config/programs?count…4946-b696-f4bd84f00a96 could save 14.5KiB (86% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 523B (14% reduction).

Minifying https://s.adroll.com/pixel/W2GJ334XQFAOZH5MXFWDBH/…E2ALZUZFWZN4ZWIL7JQ.js could save 523B (14% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 547B (14% reduction).

Minifying https://www.landr.com/ could save 547B (14% reduction) after compression.

landr.com Mobile Resource Breakdown

Total Resources	117
Number of Hosts	34
Static Resources	24
JavaScript Resources	19
CSS Resources	1

landr.com mobile page usability

Last tested: 2017-06-03

Mobile Usability Medium

67/100

landr.com Mobile Usability Test Quick Summary

priority - 31Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

MASTER A TRACK and 5 others render only 4 pixels tall (12 CSS pixels).

SIGN UP FREE renders only 5 pixels tall (16 CSS pixels).

LOG IN renders only 4 pixels tall (12 CSS pixels).

AUDIO MASTERING and 1 others render only 5 pixels tall (16 CSS pixels).

Sound like a p…dio mastering. and 1 others render only 5 pixels tall (16 CSS pixels).

Sign Up Now renders only 5 pixels tall (16 CSS pixels).

DRAG YOUR TRACK HERE renders only 5 pixels tall (16 CSS pixels).

or click on and 1 others render only 5 pixels tall (16 CSS pixels).

Sound like a pro and 1 others render only 7 pixels tall (20 CSS pixels).

without paying studio rates and 1 others render only 7 pixels tall (20 CSS pixels).

Amazing Sound and 2 others render only 6 pixels tall (18 CSS pixels).

Drag-and-drop…and download! and 14 others render only 4 pixels tall (12 CSS pixels).

free renders only 4 pixels tall (12 CSS pixels).

Classifying and 2 others render only 5 pixels tall (17 CSS pixels).

Identifying Production Styles and 1 others render only 8 pixels tall (24 CSS pixels).

LANDR looks at…e fingerprint. and 1 others render only 4 pixels tall (12 CSS pixels).

Pre-processing renders only 8 pixels tall (24 CSS pixels).

Based on what…or your track. renders only 4 pixels tall (12 CSS pixels).

Listen renders only 8 pixels tall (24 CSS pixels).
ELECTRONIC renders only 5 pixels tall (16 CSS pixels).
SONGWRITER and 2 others render only 5 pixels tall (16 CSS pixels).
"LANDR can act…r themselves." renders only 5 pixels tall (16 CSS pixels).
Fever renders only 5 pixels tall (16 CSS pixels).
Original renders only 5 pixels tall (17 CSS pixels).
Mastered renders only 5 pixels tall (17 CSS pixels).
Try LANDR free renders only 6 pixels tall (18 CSS pixels).
on your music renders only 6 pixels tall (18 CSS pixels).
SAVE UP TO 37% renders only 4 pixels tall (14 CSS pixels).
YEARLY renders only 4 pixels tall (12 CSS pixels).
MONTHLY renders only 4 pixels tall (12 CSS pixels).
Small files that sound great. and 2 others render only 4 pixels tall (14 CSS pixels).
mo and 5 others render only 8 pixels tall (24 CSS pixels).
$108/yr – and 5 others render only 5 pixels tall (16 CSS pixels).
SAVE 32% and 2 others render only 5 pixels tall (16 CSS pixels).
UNLIMITED and 7 others render only 4 pixels tall (14 CSS pixels).
HD WAV $19.99 / track and 12 others render only 4 pixels tall (14 CSS pixels).
RECOMMENDED renders only 3 pixels tall (11 CSS pixels).
All prices are in USD renders only 4 pixels tall (12 CSS pixels).
and get 2 LO-R…P3s per month. and 1 others render only 4 pixels tall (14 CSS pixels).
Create a free account renders only 4 pixels tall (14 CSS pixels).
It’s one of th…I’m releasing. and 7 others render only 8 pixels tall (24 CSS pixels).
Sie Medway Smith and 7 others render only 4 pixels tall (14 CSS pixels).
LANDR ACADEMY and 2 others render only 4 pixels tall (12 CSS pixels).
How to Promote Your Music and 12 others render only 4 pixels tall (12 CSS pixels).
Los Angeles and 2 others render only 4 pixels tall (12 CSS pixels).
Montreal, Queb…anada, H2T 1A8 and 7 others render only 4 pixels tall (12 CSS pixels).
English renders only 4 pixels tall (12 CSS pixels).
©LANDR 2017 Al…ghts Reserved. renders only 4 pixels tall (12 CSS pixels).

priority - 10Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

priority - 8Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/en/about" class="navbar-link">About</a> and 3 others are close to other tap targets.

The tap target <li class="first active">ELECTRONIC</li> and 1 others are close to other tap targets.
The tap target <li>INDIE</li> and 1 others are close to other tap targets.
The tap target <a></a> is close to 2 other tap targets.
The tap target <a href="http://www.all…6381/biography">Lenny Waronker</a> and 7 others are close to other tap targets.
The tap target <a href="/en" class="ng-scope">Master a Track</a> and 12 others are close to other tap targets.
The tap target <a href="https://www.fa…com/LANDRmusic"></a> and 2 others are close to other tap targets.
The tap target <a href="https://soundc…om/landr_music"></a> is close to 1 other tap targets.

landr.com HTML validation

Errors

Bad value “{{$root.Session.getCurrentLanguage()}}” for attribute “lang” on element “html”: Subtags must not exceed 8 characters in length.

Line: 2 Column: 16 - 52
"...type html> <html lang="{{$root.Session.getCurrentLanguage()}}"> <head..."

Attribute “ng-bind-template” not allowed on element “title” at this point.

Line: 4 Column: 2 - 56
"...me/ns#"> <title ng-bind-template="{{ meta.title | translate }}">LANDR<..."

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 12 Column: 5 - 68
"...f-8"> <meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible" /> ..."

Bad value “Public-Key-Pins” for attribute “http-equiv” on element “meta”.

Line: 14 Column: 5 - 124
"... /> <meta http-equiv="Public-Key-Pins" content="pin-sha256='sW+2XERgp5Lk1y2Z4EIm3nuXHcHx0ygDxnmWm8/ynSk='; max-age=2592000"> <..."

Bad value “Strict-Transport-Security” for attribute “http-equiv” on element “meta”.

Line: 15 Column: 5 - 85
"...000"> <meta http-equiv="Strict-Transport-Security" content="max-age=15552000; preload"> <..."

Bad value “X-Content-Type-Options” for attribute “http-equiv” on element “meta”.

Line: 16 Column: 5 - 64
"...oad"> <meta http-equiv="X-Content-Type-Options" content="nosniff"> <..."

Bad value “X-Frame-Options” for attribute “http-equiv” on element “meta”.

Line: 17 Column: 5 - 54
"...iff"> <meta http-equiv="X-Frame-Options" content="DENY"> ..."

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 20 Column: 5 - 93
"...a --> <meta http-equiv="content-language" content="{{$root.Session.getCurrentLanguageCode()}}"> ..."