Access faq.dash.com.sg. Help | All-In-One Mobile Wallet | Send Money

name

value

score

weighting

FCP (First Contentful Paint)

Value14.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value35.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value49.8 s

0/100

10%

31 ms

190 ms

styles.v1.css

2185 ms

scripts.v1.js

3022 ms

css2

54 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Faq.dash.com.sg, 11% (2 requests) were made to Dash.com.sg and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Dashrevamp.s3-ap-southeast-1.amazonaws.com.

Content Size

7.9 MB

After Optimization

2.0 MB

In fact, the total size of Faq.dash.com.sg main page is 7.9 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. 15% of websites need less resources to load. Javascripts take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-96%

Potential reduce by 815.6 kB

Original 853.6 kB
After minification 214.8 kB
After compression 38.1 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 638.8 kB, which is 75% 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 815.6 kB or 96% of the original size.

Image Optimization

-1%

Potential reduce by 7.5 kB

Original 654.9 kB
After minification 647.5 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. Faq Dash images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 4.0 MB

Original 5.3 MB
After minification 5.3 MB
After compression 1.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 4.0 MB or 77% of the original size.

CSS Optimization

-92%

Potential reduce by 998.8 kB

Original 1.1 MB
After minification 837.0 kB
After compression 88.4 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. Faq.dash.com.sg needs all CSS files to be minified and compressed as it can save up to 998.8 kB or 92% of the original size.

Requests Now

After Optimization

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faq Dash. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

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/).

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 Faq.dash.com.sg 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 Faq.dash.com.sg 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 Faq Dash. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: