Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 35

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

faom.org.mo

澳門工會聯合總會

Page Load Speed

63.6 sec in total

First Response

8.4 sec

Resources Loaded

54 sec

Page Rendered

1.3 sec

About Website

Click here to check amazing Faom content for Macao. Otherwise, check out these important facts you probably never knew about faom.org.mo

澳門工會聯合總會,澳門工會聯合總會,

Visit faom.org.mo

Key Findings

We analyzed Faom.org.mo page load time and found that the first response time was 8.4 sec and then it took 55.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 35 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

faom.org.mo performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value42.1 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.399

25/100

15%

TTI (Time to Interactive)

Value34.1 s

0/100

10%

Network Requests Diagram

portal.php

8363 ms

style_5_common.css

16531 ms

style.css

850 ms

jquery-1.7.1.js

19038 ms

common.js

9427 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 72% of them (93 requests) were addressed to the original Faom.org.mo, 11% (14 requests) were made to Scontent.xx.fbcdn.net and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Faom.org.mo.

Page Optimization Overview & Recommendations

Page size can be reduced by 398.7 kB (52%)

Content Size

761.7 kB

After Optimization

363.0 kB

In fact, the total size of Faom.org.mo main page is 761.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 331.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 61.2 kB

  • Original 78.6 kB
  • After minification 68.1 kB
  • After compression 17.4 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 10.5 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 61.2 kB or 78% of the original size.

Image Optimization

-21%

Potential reduce by 49.1 kB

  • Original 235.8 kB
  • After minification 186.7 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. Obviously, Faom needs image optimization as it can save up to 49.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 197.3 kB

  • Original 331.2 kB
  • After minification 294.6 kB
  • After compression 133.9 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 197.3 kB or 60% of the original size.

CSS Optimization

-78%

Potential reduce by 91.1 kB

  • Original 116.1 kB
  • After minification 112.9 kB
  • After compression 25.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. Faom.org.mo needs all CSS files to be minified and compressed as it can save up to 91.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (38%)

Requests Now

93

After Optimization

58

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

Accessibility Review

faom.org.mo accessibility score

35

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

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

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

faom.org.mo 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

faom.org.mo SEO score

92

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

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faom.org.mo can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Faom.org.mo 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 Faom. 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: