Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

whyewah.com

Welcome to Whye Wah Development & Construction Pte Ltd

Page Load Speed

5.2 sec in total

First Response

1 sec

Resources Loaded

4.1 sec

Page Rendered

95 ms

About Website

Click here to check amazing Whye Wah content. Otherwise, check out these important facts you probably never knew about whyewah.com

WHYE WAH DEVELOPMENT & CONSTRUCTION (PTE) LTD has substantial experience in all stages of construction representation in Singapore and abroad. Our construction practice involves representation of all ...

Visit whyewah.com

Key Findings

We analyzed Whyewah.com page load time and found that the first response time was 1 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whyewah.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.17

70/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

1037 ms

general.css

697 ms

general.js

736 ms

logo.jpg

740 ms

icon_career.jpg

234 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that all of those requests were addressed to Whyewah.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Whyewah.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.6 kB (5%)

Content Size

508.3 kB

After Optimization

484.7 kB

In fact, the total size of Whyewah.com main page is 508.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 488.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 11.2 kB

  • Original 15.0 kB
  • After minification 13.2 kB
  • After compression 3.9 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 1.8 kB, which is 12% 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 11.2 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 8.6 kB

  • Original 488.3 kB
  • After minification 479.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. Whye Wah images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.4 kB

  • Original 1.9 kB
  • After minification 1.6 kB
  • After compression 509 B

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 1.4 kB or 73% of the original size.

CSS Optimization

-78%

Potential reduce by 2.4 kB

  • Original 3.1 kB
  • After minification 2.2 kB
  • After compression 687 B

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. Whyewah.com needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

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

Accessibility Review

whyewah.com accessibility score

61

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

whyewah.com best practices score

75

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

Serves images with low resolution

SEO Factors

whyewah.com SEO score

58

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whyewah.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Whyewah.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 description is not detected on the main page of Whye Wah. 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: