Tools & Wizards About Us
crownregency.com.my screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

crownregency.com.my

crownregency

Page Load Speed

11.7 sec in total

First Response

1.3 sec

Resources Loaded

9.9 sec

Page Rendered

502 ms

crownregency.com.my screenshot

About Website

Click here to check amazing Crownregency content. Otherwise, check out these important facts you probably never knew about crownregency.com.my

Visit crownregency.com.my

Key Findings

We analyzed Crownregency.com.my page load time and found that the first response time was 1.3 sec and then it took 10.4 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

crownregency.com.my performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value20.2 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

www.crownregency.com.my

1256 ms

748ec8f7baf94217e4fbe2f0d04c6c4e.css

987 ms

jquery.min.js

1065 ms

jquery-migrate.min.js

791 ms

jquery.blockUI.min.js

792 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 87% of them (106 requests) were addressed to the original Crownregency.com.my, 11% (14 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Crownregency.com.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.1 kB (6%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 86.3 kB

  • Original 106.0 kB
  • After minification 98.6 kB
  • After compression 19.7 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 86.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 1.3 MB
  • After minification 1.3 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. Crownregency images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 55.7 kB

  • Original 987.5 kB
  • After minification 987.4 kB
  • After compression 931.8 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

-0%

Potential reduce by 0 B

  • Original 182.7 kB
  • After minification 182.7 kB
  • After compression 182.7 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. Crownregency.com.my has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 94 (90%)

Requests Now

105

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.crownregency.com.my

www.crownregency.com.my

1256 ms

748ec8f7baf94217e4fbe2f0d04c6c4e.css

748ec8f7baf94217e4fbe2f0d04c6c4e.css

987 ms

jquery.min.js

jquery.min.js

1065 ms

jquery-migrate.min.js

jquery-migrate.min.js

791 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

792 ms

add-to-cart.min.js

add-to-cart.min.js

960 ms

js.cookie.min.js

js.cookie.min.js

972 ms

woocommerce.min.js

woocommerce.min.js

1080 ms

v4-shims.min.js

v4-shims.min.js

1081 ms

script-elementor.js

script-elementor.js

1342 ms

script-elementor.js

script-elementor.js

1344 ms

appear.js

appear.js

1341 ms

odometer.min.js

odometer.min.js

1343 ms

imagesloaded.min.js

imagesloaded.min.js

1344 ms

masonry.min.js

masonry.min.js

1344 ms

lazysizes.min.js

lazysizes.min.js

1476 ms

jquery.nav.js

jquery.nav.js

1596 ms

rellax.min.js

rellax.min.js

1542 ms

aos.js

aos.js

1616 ms

tilt.jquery.min.js

tilt.jquery.min.js

1577 ms

circle-progress.js

circle-progress.js

1580 ms

plyr.js

plyr.js

1719 ms

countdown.js

countdown.js

1798 ms

slick.js

slick.js

2103 ms

beerslider.js

beerslider.js

1845 ms

jarallax.js

jarallax.js

1915 ms

flex-images.js

flex-images.js

1938 ms

fitvideos.js

fitvideos.js

1965 ms

highlight.js

highlight.js

2055 ms

custom.js

custom.js

2117 ms

index.js

index.js

2233 ms

index.js

index.js

2262 ms

core.min.js

core.min.js

2211 ms

menu.min.js

menu.min.js

2312 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

2365 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

2371 ms

api.js

api.js

37 ms

wp-polyfill.min.js

wp-polyfill.min.js

2456 ms

dom-ready.min.js

dom-ready.min.js

1768 ms

hooks.min.js

hooks.min.js

1864 ms

i18n.min.js

i18n.min.js

1616 ms

a11y.min.js

a11y.min.js

1662 ms

autocomplete.min.js

autocomplete.min.js

1597 ms

moment.min.js

moment.min.js

1631 ms

main.js

main.js

2724 ms

locales-all.js

locales-all.js

1491 ms

jquery.datetimepicker.js

jquery.datetimepicker.js

1553 ms

ova-brw-frontend.min.js

ova-brw-frontend.min.js

1959 ms

sourcebuster.min.js

sourcebuster.min.js

1579 ms

order-attribution.min.js

order-attribution.min.js

1610 ms

react.min.js

react.min.js

1744 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

31 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

57 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

59 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

59 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

58 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

58 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

60 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

60 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

60 ms

deprecated.min.js

deprecated.min.js

1805 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

62 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

63 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

62 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

62 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

60 ms

dom.min.js

dom.min.js

1708 ms

react-dom.min.js

react-dom.min.js

1658 ms

escape-html.min.js

escape-html.min.js

1769 ms

element.min.js

element.min.js

1840 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

1852 ms

keycodes.min.js

keycodes.min.js

1827 ms

priority-queue.min.js

priority-queue.min.js

1899 ms

compose.min.js

compose.min.js

1803 ms

private-apis.min.js

private-apis.min.js

1839 ms

redux-routine.min.js

redux-routine.min.js

1778 ms

data.min.js

data.min.js

1773 ms

lodash.min.js

lodash.min.js

1916 ms

wc-blocks-registry.js

wc-blocks-registry.js

1891 ms

url.min.js

url.min.js

1830 ms

api-fetch.min.js

api-fetch.min.js

1820 ms

wc-settings.js

wc-settings.js

1764 ms

data-controls.min.js

data-controls.min.js

1917 ms

html-entities.min.js

html-entities.min.js

1852 ms

notices.min.js

notices.min.js

1870 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

1842 ms

wc-blocks-data.js

wc-blocks-data.js

1898 ms

primitives.min.js

primitives.min.js

1766 ms

warning.min.js

warning.min.js

1822 ms

blocks-components.js

blocks-components.js

1899 ms

blocks-checkout.js

blocks-checkout.js

1802 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

1821 ms

owl.carousel.min.js

owl.carousel.min.js

1847 ms

script.js

script.js

1881 ms

woo.js

woo.js

1804 ms

index.js

index.js

1840 ms

menu-canvas.js

menu-canvas.js

1871 ms

owl.carousel.min.js

owl.carousel.min.js

1783 ms

room-list-carousel.js

room-list-carousel.js

1682 ms

slick.min.js

slick.min.js

1763 ms

testimonial.js

testimonial.js

1706 ms

switch-language.js

switch-language.js

1725 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1701 ms

webpack.runtime.min.js

webpack.runtime.min.js

1688 ms

frontend-modules.min.js

frontend-modules.min.js

1691 ms

frontend.min.js

frontend.min.js

1702 ms

waypoints.min.js

waypoints.min.js

1796 ms

frontend.min.js

frontend.min.js

1570 ms

elements-handlers.min.js

elements-handlers.min.js

1641 ms

sticky-effect.js

sticky-effect.js

1613 ms

ovaicon.ttf

ovaicon.ttf

1744 ms

icomoon.ttf

icomoon.ttf

1694 ms

logo.png

logo.png

1554 ms

322499361_972128637530538_6247723111162948006_n-768x421.jpg

322499361_972128637530538_6247723111162948006_n-768x421.jpg

1995 ms

IMG_1407-768x660.jpg

IMG_1407-768x660.jpg

1851 ms

IMG_1358-768x660.jpg

IMG_1358-768x660.jpg

1875 ms

IMG_1209-768x660.jpg

IMG_1209-768x660.jpg

1971 ms

IMG_1531-768x660.jpg

IMG_1531-768x660.jpg

1934 ms

still-life-daisy-flowers-e1704701402809.jpg

still-life-daisy-flowers-e1704701402809.jpg

1634 ms

idyllic-mountain-landscape-alps-mountain-chalet-meadows-blue-sky-scaled.jpg

idyllic-mountain-landscape-alps-mountain-chalet-meadows-blue-sky-scaled.jpg

2559 ms

c189d32e2bb9114903da8f71ae594a35.jpg

c189d32e2bb9114903da8f71ae594a35.jpg

2130 ms

recaptcha__en.js

recaptcha__en.js

25 ms

Accessibility Review

crownregency.com.my accessibility score

92

Accessibility Issues

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

Buttons do not have an accessible name

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

crownregency.com.my 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

crownregency.com.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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crownregency.com.my 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 Crownregency.com.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

crownregency.com.my

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