Tools & Wizards About Us
metservice.intnet.mu screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

metservice.intnet.mu

Mauritius Meteorological Services

Page Load Speed

9.1 sec in total

First Response

842 ms

Resources Loaded

8.1 sec

Page Rendered

172 ms

metservice.intnet.mu screenshot

About Website

Welcome to metservice.intnet.mu homepage info - get ready to check Metservice Intnet best content for Mauritius right away, or after learning these important things about metservice.intnet.mu

The Mauritius Meteorological Services website ...

Visit metservice.intnet.mu

Key Findings

We analyzed Metservice.intnet.mu page load time and found that the first response time was 842 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

metservice.intnet.mu performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.104

89/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

metservice.intnet.mu

842 ms

jquery.min.js

845 ms

common.css

561 ms

style.css

562 ms

menu.css

567 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 94% of them (34 requests) were addressed to the original Metservice.intnet.mu, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Metservice.intnet.mu.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.2 kB (13%)

Content Size

1.0 MB

After Optimization

901.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metservice.intnet.mu main page is 1.0 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 924.2 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 48.9 kB

  • Original 53.6 kB
  • After minification 32.1 kB
  • After compression 4.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 21.4 kB, which is 40% 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 48.9 kB or 91% of the original size.

Image Optimization

-9%

Potential reduce by 84.9 kB

  • Original 924.2 kB
  • After minification 839.3 kB

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. Metservice Intnet images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 239 B

  • Original 52.6 kB
  • After minification 52.6 kB
  • After compression 52.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-20%

Potential reduce by 1.2 kB

  • Original 6.2 kB
  • After minification 6.2 kB
  • After compression 5.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. Metservice.intnet.mu needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (23%)

Requests Now

35

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metservice.intnet.mu

metservice.intnet.mu

842 ms

jquery.min.js

jquery.min.js

845 ms

common.css

common.css

561 ms

style.css

style.css

562 ms

menu.css

menu.css

567 ms

bjqs.css

bjqs.css

577 ms

bjqs-1.3.min.js

bjqs-1.3.min.js

579 ms

stop.js

stop.js

1124 ms

slider.css

slider.css

1128 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

1128 ms

mms-logo.png

mms-logo.png

285 ms

mauritius_flag.png

mauritius_flag.png

550 ms

logo-1.png

logo-1.png

551 ms

home.png

home.png

561 ms

menumore.png

menumore.png

580 ms

meteohp-myt-weather.jpg

meteohp-myt-weather.jpg

1158 ms

cloudy.png

cloudy.png

848 ms

partly%20cloudy%20night.png

partly%20cloudy%20night.png

1112 ms

meteobg.jpg

meteobg.jpg

3079 ms

rodrigues.jpg

rodrigues.jpg

1120 ms

bullets_arrow.png

bullets_arrow.png

1135 ms

sep1.png

sep1.png

1406 ms

fine-night.png

fine-night.png

2225 ms

wave.png

wave.png

1680 ms

partly-cloudy-day.png

partly-cloudy-day.png

1699 ms

cloudy-with-showers.png

cloudy-with-showers.png

2553 ms

partly-cloudy-with-showers-day.png

partly-cloudy-with-showers-day.png

1966 ms

shadow1.png

shadow1.png

2242 ms

portlouisforecast.jpg

portlouisforecast.jpg

2264 ms

red.jpg

red.jpg

2531 ms

blue.jpg

blue.jpg

2772 ms

seabg.jpg

seabg.jpg

6156 ms

ga.js

ga.js

15 ms

HelvNeue35.ttf

HelvNeue35.ttf

4176 ms

BEBAS___-webfont.woff

BEBAS___-webfont.woff

3040 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

metservice.intnet.mu accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

metservice.intnet.mu 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

metservice.intnet.mu SEO score

75

Search Engine Optimization Advices

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 Metservice.intnet.mu 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 Metservice.intnet.mu 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

metservice.intnet.mu

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