2 sec in total
315 ms
1.3 sec
408 ms
Click here to check amazing WebSMS content for Sri Lanka. Otherwise, check out these important facts you probably never knew about websms.lk
Best SMS Gateway to Sri Lanka with OTP SMS APIs for Mobile Number Verification. Try Our Low Cost SMS Gateway Service to reach your Clients Effectively. Promote your Business today using Bulk SMS Servi...
Visit websms.lkWe analyzed Websms.lk page load time and found that the first response time was 315 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
websms.lk performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value16.6 s
0/100
25%
Value11.0 s
6/100
10%
Value630 ms
47/100
30%
Value1.464
0/100
15%
Value16.1 s
6/100
10%
315 ms
41 ms
83 ms
61 ms
70 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 72% of them (74 requests) were addressed to the original Websms.lk, 13% (13 requests) were made to Embed.tawk.to and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (459 ms) belongs to the original domain Websms.lk.
Page size can be reduced by 621.0 kB (45%)
1.4 MB
744.4 kB
In fact, the total size of Websms.lk main page is 1.4 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 912.3 kB which makes up the majority of the site volume.
Potential reduce by 34.8 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.8 kB or 83% of the original size.
Potential reduce by 525.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. Obviously, WebSMS needs image optimization as it can save up to 525.1 kB or 58% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 51.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 51.8 kB or 15% of the original size.
Potential reduce by 9.2 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. Websms.lk needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 15% of the original size.
Number of requests can be reduced by 60 (62%)
97
37
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WebSMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
websms.lk
315 ms
css@family=Open+Sans_3A300,300italic,400,400italic,600,600italic,700,700italic,800,800italic
41 ms
css@family=Raleway_3A100,200,300,400,500,600,700,800,900
83 ms
reset.css
61 ms
style.css
70 ms
font-awesome.min.css
76 ms
responsive-leyouts.css
74 ms
sticky.css
93 ms
bootstrap.min.css
126 ms
demo.css
118 ms
menu.css
131 ms
style.css
130 ms
settings.css
162 ms
simple-line-icons.css
224 ms
flexslider.css
228 ms
accordion.css
230 ms
responsive-tabs.css
233 ms
responsive-tabs2.css
230 ms
responsive-tabs3.css
231 ms
green.css
232 ms
page.php
114 ms
email-decode.min.js
225 ms
jquery.js
241 ms
jquery-1.js
241 ms
styleselector.js
249 ms
jquery.themepunch.tools.min.js
310 ms
jquery.themepunch.revolution.min.js
318 ms
custom1.js
321 ms
bootstrap.min.js
308 ms
customeUI.js
308 ms
sticky.js
308 ms
modernizr.custom.75180.js
366 ms
responsive-tabs.min.js
362 ms
custom.js
362 ms
totop.js
359 ms
jquery.flexslider.js
377 ms
custom.js
361 ms
js
69 ms
slide1_bg.jpg
459 ms
slide1_img1.png
431 ms
slide2_img1.png
410 ms
slide3_img1.png
396 ms
site-img5.png
393 ms
site-img184.jpg
391 ms
site-img185.jpg
459 ms
site-img186.jpg
418 ms
uSNZLykqYPO.css
16 ms
7vUf4_egbf-.js
22 ms
o1ndYS2og_B.js
45 ms
guwKwycnxkZ.js
50 ms
VbCgKXRxGU7.js
49 ms
p55HfXW__mM.js
49 ms
ALTQi95mOyD.js
54 ms
j6FwKUdWUaU.js
56 ms
site-img4.jpg
395 ms
site-img13.png
381 ms
site-img14.png
383 ms
site-img15.png
375 ms
site-img16.png
424 ms
435195405_1731948227215495_8566020896160328781_n.png
275 ms
327338473_735433831231491_4467187869654012263_n.jpg
138 ms
2vViO7gHnuy.js
107 ms
UXtr_j2Fwe-.png
91 ms
site-img17.png
401 ms
site-img18.png
396 ms
payment_logo1.jpg
394 ms
payment_logo2.jpg
323 ms
payment_logo3.jpg
400 ms
payment_logo4.jpg
399 ms
payment_logo5.png
391 ms
logo.png
394 ms
timer.png
380 ms
title_line1.png
381 ms
parallax_bg2.jpg
346 ms
fontawesome-webfont.woff@v=4.2.0
376 ms
site-img1.png
349 ms
title_line3.png
352 ms
site-img2.png
340 ms
site-img3.png
372 ms
site-img19.png
371 ms
title_line4.png
350 ms
site-img20.png
349 ms
title_line5.png
360 ms
scroll-top-arrow.png
368 ms
default
239 ms
loader.gif
294 ms
large_left.png
298 ms
page.php
156 ms
large_right.png
302 ms
435195405_1731948227215495_8566020896160328781_n.png
24 ms
twk-arr-find-polyfill.js
155 ms
twk-object-values-polyfill.js
59 ms
twk-event-polyfill.js
75 ms
twk-entries-polyfill.js
160 ms
twk-iterator-polyfill.js
154 ms
twk-promise-polyfill.js
166 ms
twk-main.js
72 ms
twk-vendor.js
90 ms
twk-chunk-vendors.js
91 ms
twk-chunk-common.js
116 ms
twk-runtime.js
102 ms
twk-app.js
116 ms
Simple-Line-Icons.woff
83 ms
websms.lk 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
<frame> or <iframe> elements do not have a title
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
Heading elements are not in a sequentially-descending order
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>).
websms.lk 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
websms.lk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Websms.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 Websms.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.
websms.lk
Open Graph description is not detected on the main page of WebSMS. 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: