12.2 sec in total
808 ms
11.1 sec
268 ms
Visit yes.my now to see the best up-to-date Yes content for Malaysia and also check out these interesting facts you probably never knew about yes.my
Yes is the world's first nationwide converged 4G service that offers data, calls and SMS in one simple plan.
Visit yes.myWe analyzed Yes.my page load time and found that the first response time was 808 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yes.my performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value15.7 s
0/100
25%
Value24.9 s
0/100
10%
Value650 ms
46/100
30%
Value0.011
100/100
15%
Value15.8 s
6/100
10%
808 ms
1292 ms
751 ms
955 ms
961 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 78% of them (39 requests) were addressed to the original Yes.my, 4% (2 requests) were made to Seal.digicert.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Yes.my.
Page size can be reduced by 788.9 kB (18%)
4.3 MB
3.5 MB
In fact, the total size of Yes.my main page is 4.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. 30% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 28.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. This page needs HTML code to be minified as it can gain 11.9 kB, which is 36% 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 28.1 kB or 84% of the original size.
Potential reduce by 44.1 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. Yes images are well optimized though.
Potential reduce by 554.1 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 554.1 kB or 65% of the original size.
Potential reduce by 162.6 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. Yes.my needs all CSS files to be minified and compressed as it can save up to 162.6 kB or 85% of the original size.
Number of requests can be reduced by 11 (25%)
44
33
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yes.my
808 ms
www.yes.my
1292 ms
style.css
751 ms
landing.css
955 ms
header.css
961 ms
footer.css
975 ms
jquery.js
1238 ms
function.js
1052 ms
header.js
1748 ms
footer.js
1862 ms
Note8-Banner_mobile.jpg
727 ms
Yes-Banner-Mobile.jpg
1251 ms
MyYesApp-Banner-mobile.jpg
1448 ms
Yes-Huddle-Banner-mobile.jpg
1944 ms
huawei-samsung-mobile.jpg
1589 ms
lte-subbanner1.jpg
1597 ms
lte-subbanner1_m.jpg
1890 ms
yes_altitude_subbanner.jpg
2703 ms
yes_altitude_subbanner_m.jpg
2770 ms
panel-channel.jpg
2743 ms
panel-channel_m.jpg
2782 ms
lte-subbanner4.jpg
3024 ms
lte-subbanner4_m.jpg
2971 ms
gtm.js
95 ms
yes_logo.png
3505 ms
sprite-header.png
3956 ms
Note8-Banner_desktop.jpg
4417 ms
Yes-Banner-Desktop.jpg
4463 ms
MyYesApp-Banner-desktop.jpg
4426 ms
Yes-Huddle-Banner-desktop.jpg
5153 ms
huawei-samsung-web.jpg
5253 ms
wall-bg.jpg
5428 ms
wooden-rack.png
5864 ms
seal.min.js
58 ms
footer-arr-top.png
5285 ms
logo-ctm.png
5699 ms
sprite-footer.png
6363 ms
vagron-webfont.woff
6424 ms
vagroln-webfont.woff
6653 ms
roboto-medium-webfont.woff
6588 ms
roboto-regular-webfont.woff
6927 ms
analytics.js
27 ms
src=5782640;type=invmedia;cat=lhdo3txm;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=9296235581859.945
51 ms
fbevents.js
81 ms
collect
12 ms
1046001702104384
15 ms
Pix-1x1.gif
25 ms
16 ms
4 ms
129 ms
yes.my 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.
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
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
yes.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
yes.my SEO score
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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yes.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 Yes.my main page’s claimed encoding is iso-8859-1. 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.
yes.my
Open Graph data is detected on the main page of Yes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: