Tools & Wizards About Us
ezie.app screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ezie.app

Cheapest Courier Service in Singapore | EZIE Logistics

Page Load Speed

2.8 sec in total

First Response

80 ms

Resources Loaded

2.7 sec

Page Rendered

53 ms

ezie.app screenshot

About Website

Visit ezie.app now to see the best up-to-date EZIE content for Singapore and also check out these interesting facts you probably never knew about ezie.app

In need of an affordable courier service in Singapore? EZIE Logistics is a professional courier that provides customers with quality & cheap courier services

Visit ezie.app

Key Findings

We analyzed Ezie.app page load time and found that the first response time was 80 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ezie.app performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value5,970 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.869

4/100

15%

TTI (Time to Interactive)

Value32.8 s

0/100

10%

Network Requests Diagram

ezie.app

80 ms

ezie.app

49 ms

css2

33 ms

css2

64 ms

surly-badges.min.css

141 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 13% of them (6 requests) were addressed to the original Ezie.app, 15% (7 requests) were made to Fonts.gstatic.com and 13% (6 requests) were made to Assetscdn-wchat.freshchat.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Umlazada.alibaba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.8 kB (1%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ezie.app main page is 1.7 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. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 9.5 kB

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 6.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. 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 9.5 kB or 59% of the original size.

JavaScript Optimization

-0%

Potential reduce by 3.9 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 1.5 MB

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

-0%

Potential reduce by 460 B

  • Original 136.4 kB
  • After minification 136.4 kB
  • After compression 135.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. Ezie.app has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (84%)

Requests Now

37

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ezie.app

ezie.app

80 ms

ezie.app

ezie.app

49 ms

css2

css2

33 ms

css2

css2

64 ms

surly-badges.min.css

surly-badges.min.css

141 ms

41 ms

50465c5995.js

50465c5995.js

68 ms

js

js

127 ms

js

js

270 ms

securesdk_lzd_v1.js

securesdk_lzd_v1.js

355 ms

18.528f980e.chunk.css

18.528f980e.chunk.css

62 ms

main.31c78328.chunk.css

main.31c78328.chunk.css

66 ms

18.76f75cb4.chunk.js

18.76f75cb4.chunk.js

135 ms

main.e908d035.chunk.js

main.e908d035.chunk.js

118 ms

css2

css2

15 ms

fbevents.js

fbevents.js

140 ms

gtm.js

gtm.js

140 ms

branch-latest.min.js

branch-latest.min.js

196 ms

196 ms

205 ms

track.js

track.js

88 ms

34 ms

27 ms

securesdk_lzd_v1.js

securesdk_lzd_v1.js

762 ms

pt2.js

pt2.js

402 ms

widget.js

widget.js

21 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTM.ttf

24 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhRTM.ttf

33 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDshRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDshRTM.ttf

70 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmRTM.ttf

59 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmRTM.ttf

76 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmRTM.ttf

76 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImRTM.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImRTM.ttf

76 ms

widget.css

widget.css

9 ms

13 ms

vendor.d64d219ca4493f67a3970efc52d51c86.css

vendor.d64d219ca4493f67a3970efc52d51c86.css

53 ms

vendor.862630a2b93632e0d7bbae6d63246102.js

vendor.862630a2b93632e0d7bbae6d63246102.js

67 ms

211.js

211.js

167 ms

chunk.b5645190bb6494a8b04e.css

chunk.b5645190bb6494a8b04e.css

58 ms

fd-messaging.b06d3173a46f1f0dfdd0.css

fd-messaging.b06d3173a46f1f0dfdd0.css

65 ms

fd-messaging.2319169d2a82e54c07fc.js

fd-messaging.2319169d2a82e54c07fc.js

63 ms

crwjf15ch4

crwjf15ch4

248 ms

clarity.js

clarity.js

19 ms

c.gif

c.gif

7 ms

um.js

um.js

222 ms

wu.json

wu.json

1420 ms

Accessibility Review

ezie.app accessibility score

85

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

[id] attributes on active, focusable elements are not unique

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

ezie.app best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

ezie.app SEO score

76

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

High

Document doesn't have a valid hreflang

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 Ezie.app 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 Ezie.app 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

ezie.app

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