Tools & Wizards About Us
wokhey.sg screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wokhey.sg

WOK HEY | Modern Asian Stir-Fry Deliciousness

Page Load Speed

15.7 sec in total

First Response

1.2 sec

Resources Loaded

14 sec

Page Rendered

534 ms

wokhey.sg screenshot

About Website

Click here to check amazing WOK HEY content for Singapore. Otherwise, check out these important facts you probably never knew about wokhey.sg

A modern, fast-casual, convenient take-out concept. We offer tasty, nutritious, value-for-money, customisable fry-to-order rice and noodle wok dishes.

Visit wokhey.sg

Key Findings

We analyzed Wokhey.sg page load time and found that the first response time was 1.2 sec and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

wokhey.sg performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value27.0 s

0/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value41.3 s

0/100

10%

Network Requests Diagram

www.wokhey.sg

1205 ms

js

82 ms

js

164 ms

wp-emoji-release.min.js

466 ms

style.min.css

705 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 94% of them (99 requests) were addressed to the original Wokhey.sg, 4% (4 requests) were made to Googletagmanager.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Wokhey.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.2 MB (42%)

Content Size

12.4 MB

After Optimization

7.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wokhey.sg main page is 12.4 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. 70% of websites need less resources to load. Images take 11.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.0 kB

  • Original 70.7 kB
  • After minification 60.6 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 10.2 kB, which is 14% 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 56.0 kB or 79% of the original size.

Image Optimization

-41%

Potential reduce by 4.7 MB

  • Original 11.4 MB
  • After minification 6.7 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, WOK HEY needs image optimization as it can save up to 4.7 MB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-34%

Potential reduce by 181.6 kB

  • Original 529.8 kB
  • After minification 524.3 kB
  • After compression 348.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 181.6 kB or 34% of the original size.

CSS Optimization

-47%

Potential reduce by 214.2 kB

  • Original 452.0 kB
  • After minification 428.6 kB
  • After compression 237.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. Wokhey.sg needs all CSS files to be minified and compressed as it can save up to 214.2 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (73%)

Requests Now

91

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wokhey.sg

www.wokhey.sg

1205 ms

js

js

82 ms

js

js

164 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

466 ms

style.min.css

style.min.css

705 ms

dnd-upload-cf7.css

dnd-upload-cf7.css

723 ms

styles.css

styles.css

725 ms

jquery.powertip.min.css

jquery.powertip.min.css

722 ms

maps_points.css

maps_points.css

737 ms

style.css

style.css

987 ms

wp-video-popup.css

wp-video-popup.css

942 ms

close-button-icon.css

close-button-icon.css

959 ms

YouTubePopUp.css

YouTubePopUp.css

960 ms

front.min.css

front.min.css

964 ms

slick.css

slick.css

979 ms

slick-theme.css

slick-theme.css

1179 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

1207 ms

animation.css

animation.css

1433 ms

style.dev.css

style.dev.css

1925 ms

layouts.css

layouts.css

1477 ms

responsive.css

responsive.css

1237 ms

css

css

32 ms

style.css

style.css

1415 ms

shortcodes_responsive.css

shortcodes_responsive.css

1451 ms

magnific_popup.css

magnific_popup.css

1485 ms

dashicons.min.css

dashicons.min.css

1653 ms

jquery.js

jquery.js

1908 ms

jquery-migrate.min.js

jquery-migrate.min.js

1688 ms

YouTubePopUp.jquery.js

YouTubePopUp.jquery.js

1719 ms

YouTubePopUp.js

YouTubePopUp.js

1738 ms

ie-compat.min.js

ie-compat.min.js

1902 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

2162 ms

slick.min.js

slick.min.js

2201 ms

zepto.min.js

zepto.min.js

1992 ms

jquery.cloud9carousel.js

jquery.cloud9carousel.js

2140 ms

js

js

63 ms

js

js

91 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

1943 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

1959 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

2037 ms

wp-polyfill.min.js

wp-polyfill.min.js

2179 ms

element.js

element.js

66 ms

index.js

index.js

2178 ms

codedropz-uploader-min.js

codedropz-uploader-min.js

1951 ms

dnd-upload-cf7.js

dnd-upload-cf7.js

1706 ms

jquery.powertip.min.js

jquery.powertip.min.js

1732 ms

maps_points.js

maps_points.js

1774 ms

scripts.js

scripts.js

1904 ms

wp-video-popup.js

wp-video-popup.js

1891 ms

front.min.js

front.min.js

1711 ms

comment-reply.min.js

comment-reply.min.js

1693 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

1740 ms

custom.js

custom.js

1789 ms

jquery.fitvids.js

jquery.fitvids.js

1887 ms

waypoints.min.js

waypoints.min.js

1870 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

1714 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

2165 ms

common.js

common.js

1704 ms

main.js

main.js

1587 ms

wp-embed.min.js

wp-embed.min.js

1669 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1658 ms

style.css

style.css

2130 ms

style.css

style.css

1707 ms

stylesheet.css

stylesheet.css

1596 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1650 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1629 ms

logo2.png

logo2.png

260 ms

facebook.png

facebook.png

260 ms

insta.png

insta.png

258 ms

menu-icon.png

menu-icon.png

261 ms

Logo-icon.png

Logo-icon.png

261 ms

play.png

play.png

256 ms

prod1.png

prod1.png

2135 ms

element1.jpg

element1.jpg

531 ms

play1.png

play1.png

529 ms

preloader.gif

preloader.gif

531 ms

EFR-with-Seasoned-Prawns-Tobiko-1.png

EFR-with-Seasoned-Prawns-Tobiko-1.png

1947 ms

Copy-of-rice.png

Copy-of-rice.png

1724 ms

Copy-of-seafood-icon.png

Copy-of-seafood-icon.png

2135 ms

Copy-of-vegetable-icon.png

Copy-of-vegetable-icon.png

2148 ms

SHFR-with-Grilled-Chicken-Broccoli.png

SHFR-with-Grilled-Chicken-Broccoli.png

3305 ms

Copy-of-chicken-icon.png

Copy-of-chicken-icon.png

2217 ms

FR-with-Seasoned-Prawns-Asparagus-Shimeji-Mushroom.png

FR-with-Seasoned-Prawns-Asparagus-Shimeji-Mushroom.png

2433 ms

Copy-of-noodle-icon.png

Copy-of-noodle-icon.png

2378 ms

FU-with-Braised-Beef.png

FU-with-Braised-Beef.png

2612 ms

Copy-of-beef-icon.png

Copy-of-beef-icon.png

2634 ms

Group-4-1.png

Group-4-1.png

2474 ms

AvenirNext-Medium.woff

AvenirNext-Medium.woff

2561 ms

AvenirNext-Regular.woff

AvenirNext-Regular.woff

2621 ms

AvenirNext-UltraLight.woff

AvenirNext-UltraLight.woff

2673 ms

AvenirNext-DemiBold.woff

AvenirNext-DemiBold.woff

2800 ms

AvenirNext-Bold.woff

AvenirNext-Bold.woff

2814 ms

AvenirNext-Heavy.woff

AvenirNext-Heavy.woff

2815 ms

AvenirNext-MediumItalic.woff

AvenirNext-MediumItalic.woff

2871 ms

AvenirNext-Italic.woff

AvenirNext-Italic.woff

2934 ms

AvenirNext-UltraLightItalic.woff

AvenirNext-UltraLightItalic.woff

3044 ms

AvenirNext-DemiBoldItalic.woff

AvenirNext-DemiBoldItalic.woff

3056 ms

AvenirNext-BoldItalic.woff

AvenirNext-BoldItalic.woff

3083 ms

AvenirNext-HeavyItalic.woff

AvenirNext-HeavyItalic.woff

3117 ms

modules.ttf

modules.ttf

3195 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

3163 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

3173 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

3107 ms

bg2.jpg

bg2.jpg

246 ms

bg4.jpg

bg4.jpg

717 ms

Accessibility Review

wokhey.sg accessibility score

91

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.

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

wokhey.sg 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

High

Page has valid source maps

SEO Factors

wokhey.sg SEO score

93

Search Engine Optimization Advices

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

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 Wokhey.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 Wokhey.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

wokhey.sg

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