Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

prestomall.com

Page Load Speed

8.9 sec in total

First Response

1.5 sec

Resources Loaded

7.3 sec

Page Rendered

60 ms

About Website

Visit prestomall.com now to see the best up-to-date Prestomall content for Malaysia and also check out these interesting facts you probably never knew about prestomall.com

Presto - Malaysia’s First Largest Multiple Loyalty Points Redemption Hub

Visit prestomall.com

Key Findings

We analyzed Prestomall.com page load time and found that the first response time was 1.5 sec and then it took 7.4 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

prestomall.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value80.5 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value33.5 s

0/100

10%

Network Requests Diagram

prestomall.com

1496 ms

www.prestomall.com

377 ms

shop.prestoconnect.io

26 ms

presto.direct2u.store

608 ms

gtm.js

85 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Prestomall.com, 83% (64 requests) were made to Static.presto.direct and 12% (9 requests) were made to Presto.direct2u.store. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Static.presto.direct.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (19%)

Content Size

13.3 MB

After Optimization

10.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prestomall.com main page is 13.3 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. 45% of websites need less resources to load. Images take 13.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 36.0 kB

  • Original 46.6 kB
  • After minification 44.5 kB
  • After compression 10.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 36.0 kB or 77% of the original size.

Image Optimization

-19%

Potential reduce by 2.5 MB

  • Original 13.0 MB
  • After minification 10.5 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. Obviously, Prestomall needs image optimization as it can save up to 2.5 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-7%

Potential reduce by 17.0 kB

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

CSS Optimization

-69%

Potential reduce by 7.8 kB

  • Original 11.3 kB
  • After minification 9.6 kB
  • After compression 3.5 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. Prestomall.com needs all CSS files to be minified and compressed as it can save up to 7.8 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (75%)

Requests Now

72

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

prestomall.com accessibility score

87

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.

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

Document doesn't have a <title> element

High

Links do not have a discernible name

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

prestomall.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

prestomall.com SEO score

73

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prestomall.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Prestomall.com 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 data is detected on the main page of Prestomall. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: