Tools & Wizards About Us
pierrelorren.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pierrelorren.com

Pierre Lorren Jewellery - Faberge Egg, Handmade Jewelry

Page Load Speed

1 sec in total

First Response

91 ms

Resources Loaded

710 ms

Page Rendered

240 ms

pierrelorren.com screenshot

About Website

Visit pierrelorren.com now to see the best up-to-date Pierre Lorren content and also check out these interesting facts you probably never knew about pierrelorren.com

Faberge eggs, unique handmade masterpieces. Exquisite, handmade, designer jewelry. Brought to you by the most experienced artisans. Our goal: your satisfaction.

Visit pierrelorren.com

Key Findings

We analyzed Pierrelorren.com page load time and found that the first response time was 91 ms and then it took 950 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

pierrelorren.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

pierrelorren.com

91 ms

rs=w:1920,m

624 ms

script.js

17 ms

UX.4.34.11.js

21 ms

script.js

25 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Pierrelorren.com, 83% (10 requests) were made to Img1.wsimg.com and 8% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (624 ms) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.0 kB (40%)

Content Size

400.3 kB

After Optimization

239.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pierrelorren.com main page is 400.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 190.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 114.8 kB

  • Original 138.8 kB
  • After minification 138.6 kB
  • After compression 24.0 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 114.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 71.4 kB
  • After minification 71.4 kB

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. Pierre Lorren images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 46.2 kB

  • Original 190.1 kB
  • After minification 190.1 kB
  • After compression 143.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 46.2 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (57%)

Requests Now

7

After Optimization

3

  • Images
  • JavaScript

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

Network Requests Diagram

pierrelorren.com

pierrelorren.com

91 ms

rs=w:1920,m

rs=w:1920,m

624 ms

script.js

script.js

17 ms

UX.4.34.11.js

UX.4.34.11.js

21 ms

script.js

script.js

25 ms

js

js

71 ms

98 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff

35 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6VQ.woff

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6VQ.woff

24 ms

scc-c2.min.js

scc-c2.min.js

11 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lM.woff

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lM.woff

54 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lM.woff

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lM.woff

59 ms

Accessibility Review

pierrelorren.com accessibility score

89

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

button, link, and menuitem elements do not have accessible names.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pierrelorren.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pierrelorren.com SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pierrelorren.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pierrelorren.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

pierrelorren.com

Open Graph data is detected on the main page of Pierre Lorren. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: