Tools & Wizards About Us
mercur.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

mercur.com

Solutions for Budgeting, Forecasting & Reporting | Mercur

Page Load Speed

4.5 sec in total

First Response

850 ms

Resources Loaded

2.7 sec

Page Rendered

1 sec

mercur.com screenshot

About Website

Visit mercur.com now to see the best up-to-date Mercur content for Sweden and also check out these interesting facts you probably never knew about mercur.com

With Mercur you get a fast, simple, flexible, cost-efficient solution for budgeting, forecasting and reporting.

Visit mercur.com

Key Findings

We analyzed Mercur.com page load time and found that the first response time was 850 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

mercur.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.531

14/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

www.mercur.com

850 ms

gtm.js

69 ms

5722599b-beb2-4a24-9e9a-72777bd59ee7.js

386 ms

uc.js

52 ms

jquery.min.js

25 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 50% of them (25 requests) were addressed to the original Mercur.com, 4% (2 requests) were made to T.gatorleads.co.uk and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (892 ms) belongs to the original domain Mercur.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 610.2 kB (14%)

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mercur.com main page is 4.2 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. 30% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 34.8 kB

  • Original 48.3 kB
  • After minification 47.2 kB
  • After compression 13.5 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 34.8 kB or 72% of the original size.

Image Optimization

-10%

Potential reduce by 375.3 kB

  • Original 3.8 MB
  • After minification 3.4 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. Mercur images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 115.5 kB

  • Original 259.0 kB
  • After minification 235.9 kB
  • After compression 143.5 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 115.5 kB or 45% of the original size.

CSS Optimization

-83%

Potential reduce by 84.7 kB

  • Original 101.9 kB
  • After minification 100.3 kB
  • After compression 17.2 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. Mercur.com needs all CSS files to be minified and compressed as it can save up to 84.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (69%)

Requests Now

45

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.mercur.com

www.mercur.com

850 ms

gtm.js

gtm.js

69 ms

5722599b-beb2-4a24-9e9a-72777bd59ee7.js

5722599b-beb2-4a24-9e9a-72777bd59ee7.js

386 ms

uc.js

uc.js

52 ms

jquery.min.js

jquery.min.js

25 ms

jquery.min.js

jquery.min.js

28 ms

EncodeUtf8.js

EncodeUtf8.js

201 ms

Style.min.css

Style.min.css

303 ms

slick.css

slick.css

28 ms

slick.min.js

slick.min.js

36 ms

Base.css

Base.css

405 ms

Image.css

Image.css

409 ms

Base.css

Base.css

429 ms

Video.css

Video.css

433 ms

Iframe.css

Iframe.css

433 ms

shell.js

shell.js

50 ms

6029304.js

6029304.js

116 ms

StyleLater.min.css

StyleLater.min.css

442 ms

intersection-observer.js

intersection-observer.js

419 ms

Lazy.js

Lazy.js

419 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

26 ms

Script.js

Script.js

537 ms

search.js

search.js

447 ms

131 ms

197887857

197887857

284 ms

Mercur-Logotype-2021.svg

Mercur-Logotype-2021.svg

113 ms

mercur_solutions_.png

mercur_solutions_.png

380 ms

reference_NEW_white%20kopiera.png

reference_NEW_white%20kopiera.png

892 ms

Dx-Lazy-Placeholder.png

Dx-Lazy-Placeholder.png

201 ms

mercur_dator%20(kopia).png

mercur_dator%20(kopia).png

608 ms

facebook-logo.png

facebook-logo.png

215 ms

LinkedIn-logo.png

LinkedIn-logo.png

289 ms

Instagram_Logo-White.png

Instagram_Logo-White.png

295 ms

Capterra-Logo.png

Capterra-Logo.png

318 ms

248 ms

Ambit-Regular.woff

Ambit-Regular.woff

365 ms

Orbikular-Bold.woff

Orbikular-Bold.woff

377 ms

Ambit-Bold.woff

Ambit-Bold.woff

393 ms

insight.min.js

insight.min.js

49 ms

capterra_tracker.js

capterra_tracker.js

79 ms

collectedforms.js

collectedforms.js

119 ms

banner.js

banner.js

191 ms

fb.js

fb.js

67 ms

conversations-embed.js

conversations-embed.js

70 ms

6029304.js

6029304.js

130 ms

insight_tag_errors.gif

insight_tag_errors.gif

86 ms

4.5.png

4.5.png

16 ms

api.js

api.js

14 ms

frs-next.js

frs-next.js

324 ms

zi-tag.js

zi-tag.js

28 ms

Accessibility Review

mercur.com accessibility score

83

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

[role]s are not contained by their required parent element

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

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

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mercur.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mercur.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mercur.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

mercur.com

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