5.1 sec in total
946 ms
3.8 sec
344 ms
Welcome to mymobile.lk homepage info - get ready to check My Mobile best content for Sri Lanka right away, or after learning these important things about mymobile.lk
MyMobile.lk is the Best Place to Buy Mobile Phones in Sri Lanka. We offer a wide range of brands such as Apple, Samsung, Nokia, Huawei, Oppo and Xiaomi mobile phones.
Visit mymobile.lkWe analyzed Mymobile.lk page load time and found that the first response time was 946 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mymobile.lk performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value14.7 s
0/100
25%
Value7.6 s
25/100
10%
Value180 ms
92/100
30%
Value0.001
100/100
15%
Value12.2 s
15/100
10%
946 ms
132 ms
139 ms
92 ms
99 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 61% of them (68 requests) were addressed to the original Mymobile.lk, 4% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Mymobile.lk.
Page size can be reduced by 6.1 MB (38%)
16.3 MB
10.2 MB
In fact, the total size of Mymobile.lk main page is 16.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 15.0 MB which makes up the majority of the site volume.
Potential reduce by 119.6 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 52.2 kB, which is 39% 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 119.6 kB or 90% of the original size.
Potential reduce by 5.2 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. Obviously, My Mobile needs image optimization as it can save up to 5.2 MB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 498.9 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 498.9 kB or 67% of the original size.
Potential reduce by 330.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. Mymobile.lk needs all CSS files to be minified and compressed as it can save up to 330.6 kB or 84% of the original size.
Number of requests can be reduced by 57 (59%)
96
39
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
mymobile.lk
946 ms
bootstrap.min.css
132 ms
main.css
139 ms
red.css
92 ms
owl.carousel.css
99 ms
owl.transitions.css
96 ms
animate.min.css
144 ms
config.css
153 ms
style.css
154 ms
css
25 ms
font-awesome.min.css
187 ms
jquery-ui.css
6 ms
jquery-1.10.2.min.js
239 ms
jquery-ui.js
13 ms
snowstorm.js
106 ms
component.css
76 ms
modernizr.custom.js
63 ms
font-awesome.min.css
7 ms
jquery-migrate-1.2.1.js
108 ms
bootstrap.min.js
106 ms
js
6 ms
gmap3.min.js
108 ms
bootstrap-hover-dropdown.min.js
107 ms
owl.carousel.min.js
107 ms
css_browser_selector.min.js
108 ms
echo.min.js
108 ms
jquery.easing-1.3.min.js
177 ms
bootstrap-slider.min.js
177 ms
jquery.raty.min.js
177 ms
jquery.prettyPhoto.min.js
177 ms
jquery.customSelect.min.js
178 ms
wow.min.js
178 ms
scripts.js
178 ms
switchstylesheet.js
178 ms
buttons.js
29 ms
classie.js
230 ms
mlpushmenu.js
230 ms
analytics.js
63 ms
fb-icon.png
175 ms
gplus-icon.png
176 ms
Mymobile_New-Logo.png
177 ms
banner-side.png
203 ms
visa.jpg
333 ms
delivery.jpg
177 ms
blank.gif
203 ms
sdk.js
90 ms
ajax.gif
160 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
67 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
68 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
69 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
68 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
67 ms
fontawesome-webfont.woff
44 ms
fontawesome-webfont.woff
318 ms
collect
23 ms
224 ms
0sTQzbapM8j.js
193 ms
0sTQzbapM8j.js
248 ms
async-buttons.js
112 ms
pview
106 ms
ui-bg_flat_75_ffffff_40x100.png
136 ms
11.jpg
300 ms
12.jpg
380 ms
13.jpg
358 ms
14.jpg
275 ms
7.jpg
446 ms
1.jpg
447 ms
3.jpg
887 ms
813_1.png
345 ms
812_1.png
1539 ms
810_1.png
478 ms
809_1.png
583 ms
808_1.png
920 ms
806_1.png
732 ms
805_1.png
1095 ms
804_1.png
667 ms
811_1.png
843 ms
807_1.png
809 ms
774_1.png
856 ms
772_1.png
932 ms
669_1.png
902 ms
668_1.png
1126 ms
667_1.png
1009 ms
665_1.png
1498 ms
sc
58 ms
like.php
124 ms
buttons.e80452d5e7cc382dad89d10f50bde247.css
35 ms
p.js
50 ms
t.dhj
17 ms
4qFiRLLPSF7.js
116 ms
lH1ibRl5GKq.png
114 ms
t.dhj
6 ms
t_.js
9 ms
generic
9 ms
generic
12 ms
tpid=CvQBA1mvmTsAAAARJ47qAw%3D%3D
14 ms
pixel
26 ms
generic
10 ms
ttd
10 ms
cs
5 ms
pixel
15 ms
cs
18 ms
nlsn
15 ms
190 ms
50962
120 ms
generic
32 ms
5386
125 ms
green.css
231 ms
blue.css
113 ms
orange.css
46 ms
navy.css
125 ms
dark-green.css
334 ms
mymobile.lk accessibility score
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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
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
Heading elements are not in a sequentially-descending order
mymobile.lk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mymobile.lk 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 Mymobile.lk 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 Mymobile.lk 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.
mymobile.lk
Open Graph description is not detected on the main page of My Mobile. 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: