Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

st-erasmus.com

St Erasmus | Designer Costume Jewellery by Pieter Erasmus

Page Load Speed

2.5 sec in total

First Response

675 ms

Resources Loaded

1.7 sec

Page Rendered

143 ms

st-erasmus.com screenshot

About Website

Welcome to st-erasmus.com homepage info - get ready to check St Erasmus best content right away, or after learning these important things about st-erasmus.com

Designer fashion jewellery from Pieter Erasmus. For weddings, spectacular parties and red carpet events. Earrings, necklaces and bracelets.

Visit st-erasmus.com

Key Findings

We analyzed St-erasmus.com page load time and found that the first response time was 675 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

st-erasmus.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

www.st-erasmus.com

675 ms

styles.css

263 ms

widgets.css

102 ms

prototype.js

287 ms

ccard.js

110 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 96% of them (25 requests) were addressed to the original St-erasmus.com, 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (675 ms) belongs to the original domain St-erasmus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 491.3 kB (74%)

Content Size

667.1 kB

After Optimization

175.8 kB

In fact, the total size of St-erasmus.com main page is 667.1 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. 15% of websites need less resources to load. Javascripts take 368.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 10.7 kB

  • Original 14.4 kB
  • After minification 13.4 kB
  • After compression 3.7 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 10.7 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 1.8 kB

  • Original 75.4 kB
  • After minification 73.6 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. St Erasmus images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 299.8 kB

  • Original 368.2 kB
  • After minification 261.5 kB
  • After compression 68.4 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 299.8 kB or 81% of the original size.

CSS Optimization

-86%

Potential reduce by 179.0 kB

  • Original 209.0 kB
  • After minification 160.4 kB
  • After compression 30.0 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. St-erasmus.com needs all CSS files to be minified and compressed as it can save up to 179.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (52%)

Requests Now

25

After Optimization

12

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

Accessibility Review

st-erasmus.com accessibility score

82

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

st-erasmus.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

Missing source maps for large first-party JavaScript

SEO Factors

st-erasmus.com SEO score

91

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

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 St-erasmus.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 St-erasmus.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

Open Graph description is not detected on the main page of St Erasmus. 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: