Tools & Wizards About Us
mercurie.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

mercurie.com

Mercurie - Accelerating Africa's Digital Economy

Page Load Speed

717 ms in total

First Response

141 ms

Resources Loaded

511 ms

Page Rendered

65 ms

mercurie.com screenshot

About Website

Click here to check amazing Mercurie content. Otherwise, check out these important facts you probably never knew about mercurie.com

Visit mercurie.com

Key Findings

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

Performance Metrics

mercurie.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

mercurie.com

141 ms

js

68 ms

index-e6490825.css

137 ms

css2

42 ms

css2

55 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 40% of them (2 requests) were addressed to the original Mercurie.com, 40% (2 requests) were made to Fonts.googleapis.com and 20% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (141 ms) belongs to the original domain Mercurie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 473 B (7%)

Content Size

7.1 kB

After Optimization

6.7 kB

  • HTML
  • CSS

In fact, the total size of Mercurie.com main page is 7.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. Only 5% of websites need less resources to load. CSS take 6.0 kB which makes up the majority of the site volume.

HTML Optimization

-38%

Potential reduce by 416 B

  • Original 1.1 kB
  • After minification 998 B
  • After compression 687 B

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 416 B or 38% of the original size.

CSS Optimization

-1%

Potential reduce by 57 B

  • Original 6.0 kB
  • After minification 6.0 kB
  • After compression 6.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. Mercurie.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • JavaScript
  • CSS

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mercurie. According to our analytics all requests are already optimized.

Network Requests Diagram

mercurie.com

mercurie.com

141 ms

js

js

68 ms

index-e6490825.css

index-e6490825.css

137 ms

css2

css2

42 ms

css2

css2

55 ms

Accessibility Review

mercurie.com accessibility score

89

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.

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

Best Practices

mercurie.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

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

robots.txt is not valid

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mercurie.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Mercurie.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

mercurie.com

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