Tools & Wizards About Us

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

phoenixins.mu

Phoenix Insurance (Mauritius) Limited

Page Load Speed

2.4 sec in total

First Response

642 ms

Resources Loaded

1.3 sec

Page Rendered

409 ms

About Website

Visit phoenixins.mu now to see the best up-to-date Phoenix Ins content for Mauritius and also check out these interesting facts you probably never knew about phoenixins.mu

Phoenix Insurance (Mauritius) Limited , Phoenix Insurance, Vehicle , Travel , Marine , General Insurance , CSR , Mauritius Insurance.

Visit phoenixins.mu

Key Findings

We analyzed Phoenixins.mu page load time and found that the first response time was 642 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

phoenixins.mu performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.4

25/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

phoenixins.mu

642 ms

css

21 ms

font-awesome.min.css

52 ms

bootstrap.min.css

55 ms

hover-dropdown-menu.css

77 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 92% of them (45 requests) were addressed to the original Phoenixins.mu, 6% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (642 ms) belongs to the original domain Phoenixins.mu.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.6 kB (3%)

Content Size

4.1 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 16.6 kB

  • Original 21.2 kB
  • After minification 21.1 kB
  • After compression 4.6 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 16.6 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 99.5 kB

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

JavaScript Optimization

-16%

Potential reduce by 13.9 kB

  • Original 89.0 kB
  • After minification 89.0 kB
  • After compression 75.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 13.9 kB or 16% of the original size.

CSS Optimization

-8%

Potential reduce by 8.6 kB

  • Original 105.5 kB
  • After minification 105.5 kB
  • After compression 96.9 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. Phoenixins.mu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (60%)

Requests Now

43

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix Ins. 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 from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

phoenixins.mu accessibility score

64

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

Form elements do not have associated labels

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

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

phoenixins.mu 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

phoenixins.mu SEO score

96

Search Engine Optimization Advices

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

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenixins.mu 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 Phoenixins.mu main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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