Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

matilda.org

Matilda International Hospital: Your Healthcare Partner

Page Load Speed

22.4 sec in total

First Response

735 ms

Resources Loaded

21.4 sec

Page Rendered

297 ms

matilda.org screenshot

About Website

Visit matilda.org now to see the best up-to-date Matilda content for Hong Kong and also check out these interesting facts you probably never knew about matilda.org

Matilda International Hospital has offered personalised care since 1907. Discover what sets us apart and experience quality patient services today.

Visit matilda.org

Key Findings

We analyzed Matilda.org page load time and found that the first response time was 735 ms and then it took 21.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

matilda.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.6 s

0/100

25%

SI (Speed Index)

Value21.7 s

0/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.435

21/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

matilda.org

735 ms

1004 ms

i5ttlgsrjz

193 ms

gtm.js

85 ms

js

135 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 86% of them (89 requests) were addressed to the original Matilda.org, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (15.7 sec) belongs to the original domain Matilda.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (14%)

Content Size

9.4 MB

After Optimization

8.0 MB

In fact, the total size of Matilda.org main page is 9.4 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. 55% of websites need less resources to load. Images take 8.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 59.1 kB

  • Original 72.0 kB
  • After minification 62.8 kB
  • After compression 12.9 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 9.3 kB, which is 13% 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 59.1 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 338.5 kB

  • Original 8.2 MB
  • After minification 7.8 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. Matilda images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 654.4 kB

  • Original 808.5 kB
  • After minification 587.5 kB
  • After compression 154.1 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 654.4 kB or 81% of the original size.

CSS Optimization

-85%

Potential reduce by 277.1 kB

  • Original 327.5 kB
  • After minification 274.1 kB
  • After compression 50.5 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. Matilda.org needs all CSS files to be minified and compressed as it can save up to 277.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (30%)

Requests Now

93

After Optimization

65

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

Accessibility Review

matilda.org accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

matilda.org best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

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

matilda.org SEO score

79

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 Matilda.org 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 Matilda.org 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 Matilda. 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: