Tools & Wizards About Us
hongseng.my screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hongseng.my

Hong Seng Construction

Page Load Speed

8.3 sec in total

First Response

269 ms

Resources Loaded

7.7 sec

Page Rendered

274 ms

hongseng.my screenshot

About Website

Welcome to hongseng.my homepage info - get ready to check Hong Seng best content right away, or after learning these important things about hongseng.my

Visit hongseng.my

Key Findings

We analyzed Hongseng.my page load time and found that the first response time was 269 ms and then it took 8 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

hongseng.my performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

hongseng.my

269 ms

hongseng.my

57 ms

theme.min.css

26 ms

style.css

41 ms

chaty-front.min.css

31 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original Hongseng.my, 3% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Hongseng.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.8 kB (8%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hongseng.my main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 176.3 kB

  • Original 208.9 kB
  • After minification 205.7 kB
  • After compression 32.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 176.3 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 13.2 kB

  • Original 1.4 MB
  • After minification 1.4 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. Hong Seng images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.3 kB

  • Original 536.6 kB
  • After minification 536.6 kB
  • After compression 535.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

-1%

Potential reduce by 1.1 kB

  • Original 165.4 kB
  • After minification 165.3 kB
  • After compression 164.2 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. Hongseng.my has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (86%)

Requests Now

70

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hongseng.my

hongseng.my

269 ms

hongseng.my

hongseng.my

57 ms

theme.min.css

theme.min.css

26 ms

style.css

style.css

41 ms

chaty-front.min.css

chaty-front.min.css

31 ms

helper-parts.min.css

helper-parts.min.css

61 ms

main.min.css

main.min.css

65 ms

main.min.css

main.min.css

46 ms

grid.min.css

grid.min.css

40 ms

helper-parts.min.css

helper-parts.min.css

42 ms

style.min.css

style.min.css

61 ms

header-footer.min.css

header-footer.min.css

62 ms

frontend-lite.min.css

frontend-lite.min.css

87 ms

post-5.css

post-5.css

62 ms

all.min.css

all.min.css

78 ms

v4-shims.min.css

v4-shims.min.css

83 ms

public.css

public.css

95 ms

swiper.min.css

swiper.min.css

97 ms

frontend-lite.min.css

frontend-lite.min.css

99 ms

global.css

global.css

106 ms

post-24.css

post-24.css

108 ms

post-26.css

post-26.css

103 ms

post-29.css

post-29.css

99 ms

smartslider.min.css

smartslider.min.css

101 ms

css

css

112 ms

jquery.min.js

jquery.min.js

104 ms

jquery-migrate.min.js

jquery-migrate.min.js

103 ms

n2.min.js

n2.min.js

202 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

196 ms

ss-simple.min.js

ss-simple.min.js

200 ms

smartslider-backgroundanimation.min.js

smartslider-backgroundanimation.min.js

260 ms

animations.min.css

animations.min.css

197 ms

front.css

front.css

192 ms

effects.min.css

effects.min.css

221 ms

cht-front-script.min.js

cht-front-script.min.js

219 ms

main.min.js

main.min.js

219 ms

main.min.js

main.min.js

218 ms

core.min.js

core.min.js

252 ms

hello-frontend.min.js

hello-frontend.min.js

252 ms

hooks.min.js

hooks.min.js

245 ms

vue.min.js

vue.min.js

242 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

233 ms

jquery.sticky.min.js

jquery.sticky.min.js

231 ms

lazysizes.min.js

lazysizes.min.js

231 ms

isotope.min.js

isotope.min.js

217 ms

isotope-packery.min.js

isotope-packery.min.js

216 ms

modula-fancybox.min.js

modula-fancybox.min.js

215 ms

fancybox.min.js

fancybox.min.js

217 ms

jquery-modula.min.js

jquery-modula.min.js

203 ms

modula-pro.js

modula-pro.js

201 ms

webpack.runtime.min.js

webpack.runtime.min.js

194 ms

frontend-modules.min.js

frontend-modules.min.js

186 ms

waypoints.min.js

waypoints.min.js

182 ms

frontend.min.js

frontend.min.js

179 ms

elementor.js

elementor.js

180 ms

i18n.min.js

i18n.min.js

175 ms

elementor.js

elementor.js

179 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

176 ms

frontend.min.js

frontend.min.js

172 ms

elements-handlers.min.js

elements-handlers.min.js

173 ms

widgets-scripts.js

widgets-scripts.js

174 ms

underscore.min.js

underscore.min.js

174 ms

wp-util.min.js

wp-util.min.js

168 ms

frontend.min.js

frontend.min.js

82 ms

Hong-Seng-logo_Dark-Colour-Scheme.png

Hong-Seng-logo_Dark-Colour-Scheme.png

1104 ms

vision-hill-slider.jpg

vision-hill-slider.jpg

1801 ms

goldenpalm2.jpg

goldenpalm2.jpg

1698 ms

SP15-SLIDER.jpg

SP15-SLIDER.jpg

1882 ms

visionheights-slider.jpg

visionheights-slider.jpg

1700 ms

arrowprevious.png

arrowprevious.png

801 ms

arrownext.png

arrownext.png

1032 ms

Lines-2-1.png

Lines-2-1.png

1048 ms

GOTHICB.woff

GOTHICB.woff

908 ms

GOTHIC.woff

GOTHIC.woff

930 ms

simkai.woff

simkai.woff

6837 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

30 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

54 ms

Accessibility Review

hongseng.my accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

Links do not have a discernible name

Best Practices

hongseng.my best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

hongseng.my SEO score

93

Search Engine Optimization Advices

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

    ID

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hongseng.my can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Hongseng.my 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

hongseng.my

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