10.7 sec in total
2.2 sec
8.4 sec
158 ms
Welcome to istoremalaysia.com homepage info - get ready to check Istoremalaysia best content for Malaysia right away, or after learning these important things about istoremalaysia.com
Visit istoremalaysia.comWe analyzed Istoremalaysia.com page load time and found that the first response time was 2.2 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
istoremalaysia.com performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value4.1 s
80/100
10%
Value3,120 ms
2/100
30%
Value0.214
58/100
15%
Value5.1 s
75/100
10%
2157 ms
1552 ms
1833 ms
798 ms
568 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 92% of them (92 requests) were addressed to the original Istoremalaysia.com, 3% (3 requests) were made to Facebook.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Istoremalaysia.com.
Page size can be reduced by 374.9 kB (44%)
847.0 kB
472.2 kB
In fact, the total size of Istoremalaysia.com main page is 847.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 378.1 kB which makes up the majority of the site volume.
Potential reduce by 29.1 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 29.1 kB or 81% of the original size.
Potential reduce by 36.4 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. Istoremalaysia images are well optimized though.
Potential reduce by 217.6 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 217.6 kB or 68% of the original size.
Potential reduce by 91.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. Istoremalaysia.com needs all CSS files to be minified and compressed as it can save up to 91.7 kB or 83% of the original size.
Number of requests can be reduced by 39 (39%)
99
60
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Istoremalaysia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
istoremalaysia.com
2157 ms
widgetkit-de584d91.css
1552 ms
mootools-core.js
1833 ms
core.js
798 ms
caption.js
568 ms
jquery.js
2013 ms
widgetkit-1cbf3f46.js
1111 ms
all.js
12 ms
base.css
845 ms
layout.css
1063 ms
menus.css
1124 ms
modules.css
1330 ms
tools.css
1391 ms
system.css
1401 ms
extensions.css
1597 ms
custom.css
1673 ms
opensans.css
1682 ms
opensans.css
1805 ms
opensans.css
1863 ms
style.css
1954 ms
responsive.css
1961 ms
print.css
2076 ms
opensans.css
2587 ms
warp.js
2400 ms
responsive.js
2235 ms
accordionmenu.js
2239 ms
dropdownmenu.js
3039 ms
template.js
2335 ms
lightbox.js
770 ms
mediaelement-and-player.js
1877 ms
spotlight.js
569 ms
base.css
621 ms
layout.css
808 ms
menus.css
811 ms
modules.css
888 ms
tools.css
1031 ms
system.css
1079 ms
responsive.css
1070 ms
66 ms
print.css
1132 ms
menus.css
474 ms
responsive.css
283 ms
system.css
541 ms
system.css
264 ms
system-all.css
343 ms
xd_arbiter.php
23 ms
xd_arbiter.php
29 ms
ping
43 ms
logo.png
564 ms
reseller.png
534 ms
globalblue.png
808 ms
_DSC4650-448ec7f713.jpeg
583 ms
_DSC4651-9b58f46261.jpeg
265 ms
_DSC4652-5813714b78.jpeg
1210 ms
_DSC4653-4f33f0e250.jpeg
526 ms
_DSC4658-26e4871447.jpeg
1097 ms
_DSC4659-7fb5c3f8a5.jpeg
1091 ms
_DSC4660-c4442fbd10.jpeg
1107 ms
_DSC4661-1338182c74.jpeg
1129 ms
_DSC4662-1cb96f47f9.jpeg
1108 ms
_DSC4663-00c6e236ed.jpeg
1362 ms
_DSC4664-ecd8fb8bac.jpeg
1359 ms
_DSC4665-a2ef4e99b7.jpeg
1390 ms
_DSC4666-824dee592d.jpeg
1379 ms
_DSC4667-ffd74fde8e.jpeg
1420 ms
_DSC4668-90343da58e.jpeg
1491 ms
_DSC4670-3dc7027726.jpeg
1619 ms
_DSC4671-75300908cf.jpeg
1627 ms
_DSC4672-eb0ad02615.jpeg
1649 ms
_DSC4673-4f47cc480f.jpeg
1670 ms
_DSC4674-f069e4e0b8.jpeg
1712 ms
DSC_2913-8dd92eb737.jpeg
1773 ms
DSC_2914-93ca0a56e9.jpeg
1879 ms
DSC_2915-b70910da5b.jpeg
1894 ms
DSC_2917-7284b9d76b.jpeg
1917 ms
DSC_2918-2c9397d3e5.jpeg
1952 ms
DSC_2919-a826076d51.jpeg
2004 ms
DSC_2925-4ae9b4d5e0.jpeg
2056 ms
DSC_2929-4693620bd8.jpeg
2140 ms
DSC_2931-a1c7d0f6d3.jpeg
2162 ms
DSC_2940-e7a064918f.jpeg
2187 ms
DSC_2942-a2f3de9233.jpeg
2234 ms
OpenSans-Light-webfont.woff
2585 ms
like.php
72 ms
TY3MhkXpWJ-.js
33 ms
LVx-xkvaJ0b.png
21 ms
DSC_2943-61681eb31e.jpeg
2184 ms
DSC_2946-f6264f808e.jpeg
2141 ms
DSC_2947-cfd1b41825.jpeg
1908 ms
DSC_2948-0ed42ec44a.jpeg
1931 ms
DSC_2950-f7cd822d69.jpeg
1960 ms
DSC_2952-fa82df96fa.jpeg
2043 ms
DSC_2955-39d0bddf35.jpeg
1860 ms
DSC_2959-6529a69eef.jpeg
1610 ms
DSC_2960-4e9d893974.jpeg
1638 ms
module_icons.png
1696 ms
module_badges.png
1774 ms
totop_scroller.png
1779 ms
social_facebook_box_white_24.png
1720 ms
social_twitter_box_white_24.png
1611 ms
istoremalaysia.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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.
istoremalaysia.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
istoremalaysia.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Istoremalaysia.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Istoremalaysia.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.
istoremalaysia.com
Open Graph description is not detected on the main page of Istoremalaysia. 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: