Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

lucky-records.com

Lucky Records - Madonna, Mylène Farmer, Lady Gaga, Britney Spears, Kylie Minogue...

Page Load Speed

6.3 sec in total

First Response

341 ms

Resources Loaded

5.5 sec

Page Rendered

455 ms

lucky-records.com screenshot

About Website

Click here to check amazing Lucky Records content for Croatia. Otherwise, check out these important facts you probably never knew about lucky-records.com

Lucky Records, disquaire parisien spécialisé dans la pop : nouveautés et collectors de Madonna, Taylor Swift, Mylène Farmer, Sylvie Vartan, Kylie Minogue, Lady Gaga, Britney Spears, Michael Jackson, P...

Visit lucky-records.com

Key Findings

We analyzed Lucky-records.com page load time and found that the first response time was 341 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lucky-records.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value2.13

0/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

lucky-records.com

341 ms

www.lucky-records.com

488 ms

shared.css

307 ms

bootstrap-grid.css

323 ms

style.css

315 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 89% of them (82 requests) were addressed to the original Lucky-records.com, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Lucky-records.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.6 kB (7%)

Content Size

1.7 MB

After Optimization

1.6 MB

In fact, the total size of Lucky-records.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 57.2 kB

  • Original 72.5 kB
  • After minification 72.1 kB
  • After compression 15.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.2 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 2.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Lucky Records images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 44.7 kB

  • Original 440.5 kB
  • After minification 440.3 kB
  • After compression 395.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 18.4 kB

  • Original 98.9 kB
  • After minification 98.8 kB
  • After compression 80.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lucky-records.com needs all CSS files to be minified and compressed as it can save up to 18.4 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (55%)

Requests Now

84

After Optimization

38

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lucky Records. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

lucky-records.com accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

lucky-records.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lucky-records.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lucky-records.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Lucky-records.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Lucky Records. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: