13.4 sec in total
1.5 sec
11.3 sec
645 ms
Welcome to m.legostone.com.my homepage info - get ready to check M Legostone best content right away, or after learning these important things about m.legostone.com.my
stone supplier in Kuala Lumpur, KL. stone wholesaler, importer, and exporter in Petaling Jaya, PJ, Selangor, Malaysia. provide high quality natural stone products such as granite, stacked stone, natur...
Visit m.legostone.com.myWe analyzed M.legostone.com.my page load time and found that the first response time was 1.5 sec and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
m.legostone.com.my performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value10.6 s
0/100
25%
Value8.4 s
18/100
10%
Value120 ms
97/100
30%
Value0.281
43/100
15%
Value6.3 s
61/100
10%
1517 ms
43 ms
39 ms
1181 ms
309 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 23% of them (17 requests) were addressed to the original M.legostone.com.my, 69% (52 requests) were made to Cdn1.npcdn.net and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (8.7 sec) relates to the external source Cdn1.npcdn.net.
Page size can be reduced by 193.7 kB (5%)
3.9 MB
3.7 MB
In fact, the total size of M.legostone.com.my main page is 3.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. 50% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 94.0 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 18.2 kB, which is 16% 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 94.0 kB or 84% of the original size.
Potential reduce by 60.0 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. M Legostone images are well optimized though.
Potential reduce by 36.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 36.8 kB or 17% of the original size.
Potential reduce by 2.9 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. M.legostone.com.my has all CSS files already compressed.
Number of requests can be reduced by 33 (47%)
70
37
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Legostone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
m.legostone.com.my
1517 ms
gumby.css
43 ms
sweetalert2.min.css
39 ms
m_general.css
1181 ms
banner.css
309 ms
jquery.mmenu.css
488 ms
BreadCrumb.css
494 ms
style.css
47 ms
default.css
493 ms
nivo-slider.css
495 ms
font-awesome.css
45 ms
owl.carousel.min.css
49 ms
owl.theme.default.min.css
48 ms
animate.css
50 ms
jquery-3.2.1.min.js
54 ms
jquery-migrate-3.0.0.min.js
29 ms
owl.carousel.min.js
57 ms
sweetalert2.min.js
60 ms
slick.css
58 ms
slick-theme.css
63 ms
slick.min.js
65 ms
jquery-ui.min.js
67 ms
janimate.js
69 ms
janimate.css
71 ms
jquery.infinitescroll.js
504 ms
addthis_widget.js
144 ms
jquery.fancybox.js
75 ms
jquery.fancybox.css
76 ms
jquery-ui.min.css
79 ms
jquery-ui.theme.min.css
79 ms
m_style.css
853 ms
timeline.css
1303 ms
jquery.nivo.slider.js
1291 ms
jquery.jBreadCrumb.1.1.js
496 ms
jquery.mmenu.js
502 ms
jquery.matchHeight.js
501 ms
swiper-min.js
521 ms
fbevents.js
24 ms
xfbml.customerchat.js
51 ms
header726213.jpg
981 ms
1415758251337e971439da0ca95f3eb95f945e8865.jpg
2006 ms
1415758362newlogo.jpg
1124 ms
168024638748f4a39a668c460488cbd9a3f3071e3a.png
1592 ms
168024642332e2a0d906ab6e2889d1ad08bd88bb82.png
1803 ms
16802477081d545d81d33b346a605a3e09b4aa7d01.png
1939 ms
1680247734cab8f993a7c33c73fabd41bf5f18c743.png
2660 ms
168023664248f3644775ff8f86cd62f723517bee82.jpg
1829 ms
168023688312427d02696c0c17b46a97b0f07fd56c.jpg
2799 ms
16802369775317705fcd8179f6d43580af5c92bf97.jpg
3238 ms
1680234884b93caf0f145d1f68d8ccac494710341a.jpg
4027 ms
168023492175c09e52f1ac4fd827c0ce47fb49ae70.jpg
4098 ms
1680234951e8716cff086fc836ac8dd4cacb1185d9.jpg
3833 ms
1680234982fe26d4703f7d38fd4d3fb0bc0db99dca.jpg
4189 ms
1680235005ba30f84ee8e6f9af55967c23d670981f.jpg
4294 ms
168023503060354902832b6dd9b3c62b5cba0c7505.jpg
4885 ms
168023327228456ba78089c541ac1ccb2363aeb454.jpg
6938 ms
1680233478e1f2ed77b428a149591c56688bdba755.jpg
5637 ms
16802335058fccdd1f5c19b4a31d18ec363520d865.jpg
5748 ms
168023358989ac4669ceadb9faa30d6ec984dd5792.jpg
5864 ms
1680233693ecb0834ef70bfbaa75c839bf4ab7da9d.jpg
6059 ms
1680233733b51a1a70cf3c073c793406fa660b6f09.jpg
6557 ms
1680227379f76e5e13f9d7508c25584d66da508118.jpg
7298 ms
1679993040c1054ac169cd6cd26b6b890c5829e0f9.jpg
7246 ms
1679993073f8e97edaef45425cacbd818ef6c00ed5.jpg
7533 ms
1679993119ecaafab49f4496f4f7257ab9c911bca0.jpg
7507 ms
16799931530f96bbacca0bef5d27a9e1b3aa250105.jpg
7859 ms
167999319079b9a17ce4f9f11e019653f095ebdf3d.jpg
8486 ms
1679993262d9ad1d445dbf672b96b6ee78f2cb8d73.jpg
8638 ms
1680231757b3b8f787dfcc8130e93554bdbd471b4d.jpg
8738 ms
google-map.png
269 ms
waze.png
518 ms
reload.png
346 ms
fontawesome-webfont.woff
8216 ms
overlay-white.png
304 ms
cryptographp.inc.php
533 ms
m.legostone.com.my accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
m.legostone.com.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
m.legostone.com.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.legostone.com.my 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 M.legostone.com.my main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
m.legostone.com.my
Open Graph data is detected on the main page of M Legostone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: