Tools & Wizards About Us
ezie.app screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

ezie.app

Cheapest Courier Service in Singapore | EZIE Logistics

Page Load Speed

3.5 sec in total

First Response

111 ms

Resources Loaded

3.1 sec

Page Rendered

306 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 111 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ezie.app performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.8 s

0/100

25%

SI (Speed Index)

Value15.7 s

1/100

10%

TBT (Total Blocking Time)

Value4,160 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.8 s

0/100

10%

Network Requests Diagram

ezie.app

111 ms

ezie.app

87 ms

css2

179 ms

css2

198 ms

surly-badges.min.css

218 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 18% of them (6 requests) were addressed to the original Ezie.app, 9% (3 requests) were made to Js.stripe.com and 9% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Umlazada.alibaba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.0 kB (7%)

Content Size

229.0 kB

After Optimization

212.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ezie.app main page is 229.0 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. 50% of websites need less resources to load. Javascripts take 144.4 kB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 8.9 kB

  • Original 15.7 kB
  • After minification 15.7 kB
  • After compression 6.8 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 8.9 kB or 57% of the original size.

JavaScript Optimization

-5%

Potential reduce by 7.1 kB

  • Original 144.4 kB
  • After minification 144.4 kB
  • After compression 137.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

-0%

Potential reduce by 65 B

  • Original 68.9 kB
  • After minification 68.9 kB
  • After compression 68.8 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 25 (78%)

Requests Now

32

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 32 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 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ezie.app

ezie.app

111 ms

ezie.app

ezie.app

87 ms

css2

css2

179 ms

css2

css2

198 ms

surly-badges.min.css

surly-badges.min.css

218 ms

224 ms

50465c5995.js

50465c5995.js

206 ms

js

js

220 ms

securesdk_lzd_v1.js

securesdk_lzd_v1.js

796 ms

17.01df6f61.chunk.css

17.01df6f61.chunk.css

39 ms

main.939f8a19.chunk.css

main.939f8a19.chunk.css

135 ms

17.d833a7cd.chunk.js

17.d833a7cd.chunk.js

187 ms

main.e6a89f52.chunk.js

main.e6a89f52.chunk.js

190 ms

css2

css2

114 ms

fbevents.js

fbevents.js

180 ms

gtm.js

gtm.js

208 ms

branch-latest.min.js

branch-latest.min.js

207 ms

conversion_async.js

conversion_async.js

138 ms

912572699543241

912572699543241

91 ms

333 ms

track.js

track.js

204 ms

crwjf15ch4

crwjf15ch4

245 ms

m-outer-3437aaddcdf6922d623e172c2d6f9278.html

m-outer-3437aaddcdf6922d623e172c2d6f9278.html

34 ms

86 ms

m-outer-15a2b40a058ddff1cffdb63779fe3de1.js

m-outer-15a2b40a058ddff1cffdb63779fe3de1.js

44 ms

inner.html

inner.html

102 ms

clarity.js

clarity.js

22 ms

securesdk_lzd_v1.js

securesdk_lzd_v1.js

435 ms

pt2.js

pt2.js

190 ms

widget.js

widget.js

153 ms

page.gif

page.gif

184 ms

um.js

um.js

90 ms

c.gif

c.gif

17 ms

wu.json

wu.json

1326 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

High

Heading elements are not in a sequentially-descending order

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

85

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

ezie.app SEO score

91

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

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: