Tools & Wizards About Us
murex.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

murex.com

MX.3: the capital markets technology solution | Murex

Page Load Speed

4.5 sec in total

First Response

26 ms

Resources Loaded

3.2 sec

Page Rendered

1.3 sec

murex.com screenshot

About Website

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

Transform IT infrastructure, meet regulatory requirements and manage risk with Murex capital markets technology solutions and MX.3.

Visit murex.com

Key Findings

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

Performance Metrics

murex.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

murex.com

26 ms

www.murex.com

29 ms

en

18 ms

gtm.js

86 ms

ajax-progress.module.css

257 ms

Our browser made a total of 163 requests to load all elements on the main page. We found that 62% of them (101 requests) were addressed to the original Murex.com, 6% (10 requests) were made to Use.typekit.net and 6% (10 requests) were made to Go.murex.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Murex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 560.5 kB (27%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Murex.com main page is 2.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 51.8 kB

  • Original 63.5 kB
  • After minification 49.2 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 14.3 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 51.8 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 119.4 kB

  • Original 1.3 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. Murex images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 61.5 kB

  • Original 340.7 kB
  • After minification 340.6 kB
  • After compression 279.2 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 61.5 kB or 18% of the original size.

CSS Optimization

-74%

Potential reduce by 327.9 kB

  • Original 441.1 kB
  • After minification 389.6 kB
  • After compression 113.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. Murex.com needs all CSS files to be minified and compressed as it can save up to 327.9 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 106 (78%)

Requests Now

136

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

murex.com

murex.com

26 ms

www.murex.com

www.murex.com

29 ms

en

en

18 ms

gtm.js

gtm.js

86 ms

ajax-progress.module.css

ajax-progress.module.css

257 ms

align.module.css

align.module.css

129 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

129 ms

fieldgroup.module.css

fieldgroup.module.css

378 ms

container-inline.module.css

container-inline.module.css

129 ms

clearfix.module.css

clearfix.module.css

130 ms

details.module.css

details.module.css

344 ms

hidden.module.css

hidden.module.css

197 ms

item-list.module.css

item-list.module.css

198 ms

js.module.css

js.module.css

202 ms

nowrap.module.css

nowrap.module.css

305 ms

position-container.module.css

position-container.module.css

304 ms

progress.module.css

progress.module.css

304 ms

reset-appearance.module.css

reset-appearance.module.css

318 ms

resize.module.css

resize.module.css

357 ms

sticky-header.module.css

sticky-header.module.css

365 ms

system-status-counter.css

system-status-counter.css

371 ms

system-status-report-counters.css

system-status-report-counters.css

401 ms

system-status-report-general-info.css

system-status-report-general-info.css

427 ms

tabledrag.module.css

tabledrag.module.css

436 ms

tablesort.module.css

tablesort.module.css

448 ms

tree-child.module.css

tree-child.module.css

452 ms

views.module.css

views.module.css

607 ms

paragraphs.unpublished.css

paragraphs.unpublished.css

480 ms

normalize.css

normalize.css

505 ms

action-links.css

action-links.css

518 ms

breadcrumb.css

breadcrumb.css

528 ms

container-inline.css

container-inline.css

694 ms

details.css

details.css

558 ms

exposed-filters.css

exposed-filters.css

587 ms

field.css

field.css

598 ms

form.css

form.css

608 ms

icons.css

icons.css

642 ms

inline-form.css

inline-form.css

820 ms

item-list.css

item-list.css

682 ms

remixicon.css

remixicon.css

59 ms

all.min.css

all.min.css

49 ms

zaq1zrm.css

zaq1zrm.css

312 ms

jquery.min.js

jquery.min.js

68 ms

links.css

links.css

691 ms

menu.css

menu.css

565 ms

more-link.css

more-link.css

601 ms

pager.css

pager.css

647 ms

b4bf83015f4c39fc7b2bce3c3927aada.js

b4bf83015f4c39fc7b2bce3c3927aada.js

433 ms

landing

landing

137 ms

js

js

48 ms

destination

destination

82 ms

insight.min.js

insight.min.js

130 ms

tabledrag.css

tabledrag.css

596 ms

tableselect.css

tableselect.css

590 ms

tablesort.css

tablesort.css

581 ms

textarea.css

textarea.css

613 ms

ui-dialog.css

ui-dialog.css

551 ms

messages.css

messages.css

550 ms

progress.css

progress.css

554 ms

node.css

node.css

577 ms

insight_tag_errors.gif

insight_tag_errors.gif

150 ms

p.css

p.css

19 ms

style.css

style.css

810 ms

main.css

main.css

593 ms

custom.css

custom.css

576 ms

administration_menu-cd223fdd2b1c867ee65f64efc1e925d4.css

administration_menu-cd223fdd2b1c867ee65f64efc1e925d4.css

602 ms

contact-51956ab84d7e65f30b653c7039f2be0e.css

contact-51956ab84d7e65f30b653c7039f2be0e.css

722 ms

jquery.min.js

jquery.min.js

599 ms

once.min.js

once.min.js

616 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

589 ms

drupal.js

drupal.js

582 ms

drupal.init.js

drupal.init.js

607 ms

index.umd.min.js

index.umd.min.js

645 ms

contact-0fc14a8166ed07f884ef52f94566a361.js

contact-0fc14a8166ed07f884ef52f94566a361.js

619 ms

TweenMax.min.js

TweenMax.min.js

617 ms

popper.js

popper.js

713 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

704 ms

ScrollMagic.min.js

ScrollMagic.min.js

674 ms

aos.js

aos.js

645 ms

animation.gsap.min.js

animation.gsap.min.js

734 ms

debug.addIndicators.min.js

debug.addIndicators.min.js

835 ms

slick.min.js

slick.min.js

724 ms

modal-video.min.js

modal-video.min.js

796 ms

wow.min.js

wow.min.js

755 ms

main.js

main.js

778 ms

tag.js

tag.js

908 ms

murex.js

murex.js

742 ms

progress.js

progress.js

828 ms

loadjs.min.js

loadjs.min.js

786 ms

debounce.js

debounce.js

831 ms

announce.js

announce.js

829 ms

message.js

message.js

822 ms

ajax.js

ajax.js

820 ms

pager.js

pager.js

1011 ms

css2

css2

49 ms

css2

css2

65 ms

munchkin.js

munchkin.js

284 ms

1715291125494

1715291125494

292 ms

logo.svg

logo.svg

523 ms

ftf-award-2024-menu-thumbnail.png

ftf-award-2024-menu-thumbnail.png

526 ms

menu-hover-rabobank.jpg

menu-hover-rabobank.jpg

525 ms

Murex-Awards-2023-3%20%281%29.png

Murex-Awards-2023-3%20%281%29.png

715 ms

075c53d2-d76e-4a46-a6cb-1300abae24f3.jpeg

075c53d2-d76e-4a46-a6cb-1300abae24f3.jpeg

525 ms

cross.svg

cross.svg

660 ms

symbol11.png

symbol11.png

716 ms

symbol1.png

symbol1.png

823 ms

Big_img%402x.png

Big_img%402x.png

716 ms

HP-Square.jpg

HP-Square.jpg

717 ms

logo-white.svg

logo-white.svg

718 ms

logo-min.svg

logo-min.svg

782 ms

symbol-about.png

symbol-about.png

785 ms

play.svg

play.svg

821 ms

logo-footer.svg

logo-footer.svg

820 ms

Contact-us-EN.html

Contact-us-EN.html

466 ms

spirals.svg

spirals.svg

762 ms

Spirals-linkedin.svg

Spirals-linkedin.svg

981 ms

Oval.png

Oval.png

857 ms

spirals-2.svg

spirals-2.svg

853 ms

S6u9w4BMUTPHh7USew-FHi_o.ttf

S6u9w4BMUTPHh7USew-FHi_o.ttf

320 ms

d

d

210 ms

d

d

368 ms

S6u8w4BMUTPHh30wWyWtFCc.ttf

S6u8w4BMUTPHh30wWyWtFCc.ttf

395 ms

S6uyw4BMUTPHvxk6WQev.ttf

S6uyw4BMUTPHvxk6WQev.ttf

397 ms

d

d

369 ms

d

d

318 ms

d

d

317 ms

S6u9w4BMUTPHh6UVew-FHi_o.ttf

S6u9w4BMUTPHh6UVew-FHi_o.ttf

396 ms

d

d

367 ms

d

d

317 ms

S6u9w4BMUTPHh50Xew-FHi_o.ttf

S6u9w4BMUTPHh50Xew-FHi_o.ttf

397 ms

d

d

393 ms

remixicon.woff

remixicon.woff

232 ms

d

d

220 ms

fa-brands-400.ttf

fa-brands-400.ttf

103 ms

munchkin.js

munchkin.js

67 ms

visitWebPage

visitWebPage

537 ms

all.min.css

all.min.css

23 ms

animate.min.css

animate.min.css

30 ms

loader.js

loader.js

113 ms

forms2.min.js

forms2.min.js

108 ms

forms2.js

forms2.js

263 ms

script-cform.js

script-cform.js

216 ms

munchkin.js

munchkin.js

24 ms

stripmkttok.js

stripmkttok.js

158 ms

css2

css2

76 ms

getForm

getForm

160 ms

collect

collect

100 ms

insight_tag_errors.gif

insight_tag_errors.gif

98 ms

data-transfer-protocol.html

data-transfer-protocol.html

31 ms

matomo.js

matomo.js

109 ms

getForm

getForm

135 ms

data-transfer-protocol.html

data-transfer-protocol.html

540 ms

visitWebPage

visitWebPage

128 ms

matomo.php

matomo.php

940 ms

forms2.css

forms2.css

38 ms

forms2-theme-simple.css

forms2-theme-simple.css

39 ms

css

css

18 ms

insight_tag_errors.gif

insight_tag_errors.gif

177 ms

configs.php

configs.php

387 ms

caret-down-dark.svg

caret-down-dark.svg

571 ms

S6uyw4BMUTPHjx4wWyWtFCc.ttf

S6uyw4BMUTPHjx4wWyWtFCc.ttf

4 ms

script.js

script.js

375 ms

visitWebPage

visitWebPage

1 ms

Accessibility Review

murex.com accessibility score

88

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.

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 IDs are not unique

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

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

murex.com SEO score

86

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Murex.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 Murex.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

murex.com

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