11.8 sec in total
1.7 sec
9.8 sec
326 ms
Welcome to ours.my homepage info - get ready to check Ours best content right away, or after learning these important things about ours.my
Menjual dan membekalkan produk kesihatan dan kecantikan
Visit ours.myWe analyzed Ours.my page load time and found that the first response time was 1.7 sec and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ours.my performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value13.9 s
0/100
25%
Value12.5 s
3/100
10%
Value160 ms
94/100
30%
Value0.003
100/100
15%
Value15.2 s
7/100
10%
1684 ms
747 ms
515 ms
546 ms
551 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original Ours.my, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Ours.my.
Page size can be reduced by 553.7 kB (71%)
785.3 kB
231.6 kB
In fact, the total size of Ours.my main page is 785.3 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. 35% of websites need less resources to load. Javascripts take 494.5 kB which makes up the majority of the site volume.
Potential reduce by 34.5 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 34.5 kB or 77% of the original size.
Potential reduce by 62.5 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. Obviously, Ours needs image optimization as it can save up to 62.5 kB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 346.7 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 346.7 kB or 70% of the original size.
Potential reduce by 110.1 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. Ours.my needs all CSS files to be minified and compressed as it can save up to 110.1 kB or 82% of the original size.
Number of requests can be reduced by 31 (54%)
57
26
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ours. 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 17 to 1 for CSS and as a result speed up the page load time.
ours.my
1684 ms
k2.css
747 ms
modal.css
515 ms
normalize.css
546 ms
layout.css
551 ms
joomla.css
818 ms
system.css
777 ms
template.css
1285 ms
menu.css
1081 ms
font-awesome.css
1368 ms
gk.stuff.css
1546 ms
style1.css
1359 ms
typography.style1.css
1375 ms
css
24 ms
stylesheet.css
1588 ms
mootools-core.js
2524 ms
jquery.min.js
2621 ms
jquery-noconflict.js
1905 ms
jquery-migrate.min.js
1900 ms
core.js
2095 ms
k2.js
2118 ms
bootstrap.min.js
2677 ms
mootools-more.js
3726 ms
modal.js
2603 ms
gk.scripts.js
2670 ms
gk.menu.js
3062 ms
fitvids.jquery.js
3105 ms
script.mootools.js
3146 ms
script.mootools.js
3197 ms
engine.js
3212 ms
demo.shop_is_1gk-is-665.jpg
506 ms
banner.png
775 ms
k2.items.cache.475699d297afae315ef802312426354e_Genericnsp-659.jpg
516 ms
k2.items.cache.475699d297afae315ef802312426354e_Genericnsp-663.jpg
514 ms
k2.items.cache.0bfc0ce99892772fc285e10ee3943d9a_Genericnsp-657.jpg
516 ms
k2.items.cache.b320775de3c297425b69dccc362220a9_Genericnsp-657.jpg
532 ms
k2.items.cache.4047dc2f08c422a43c6430815243ead6_Genericnsp-657.jpg
1019 ms
k2.items.cache.8012f255a337782bffaadea968723f36_Genericnsp-657.jpg
1039 ms
k2.items.cache.d0d354668f69293e040aa69de3140c78_Genericnsp-657.jpg
1043 ms
k2.items.cache.258ee2700b8562b5d51ebf2117179b3d_Genericnsp-657.jpg
1028 ms
k2.items.cache.fedea746cd0ecb257a1249d3a2a80bb1_Genericnsp-657.jpg
1067 ms
k2.items.cache.fac9770ae986695c80dfb6c58f312f32_Genericnsp-657.jpg
1300 ms
logo1.png
1562 ms
logo2.png
1554 ms
logo3.png
1567 ms
logo4.png
1587 ms
logo5.png
1614 ms
logo6.png
1835 ms
free-shipping.png
2115 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
20 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
19 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
19 ms
gkfont.ttf
2076 ms
small.desktop.css
268 ms
tablet.css
272 ms
small.tablet.css
523 ms
mobile.css
760 ms
all.js
161 ms
demo.shop_is_2gk-is-665.jpg
540 ms
demo.shop_is_3gk-is-665.jpg
530 ms
138 ms
xd_arbiter.php
129 ms
xd_arbiter.php
250 ms
ours.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ours.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ours.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ours.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 Ours.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.
ours.my
Open Graph description is not detected on the main page of Ours. 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: