5.6 sec in total
1.6 sec
3.8 sec
164 ms
Welcome to island.lk homepage info - get ready to check Island best content for Sri Lanka right away, or after learning these important things about island.lk
Visit island.lkWe analyzed Island.lk page load time and found that the first response time was 1.6 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
island.lk performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value8.9 s
1/100
25%
Value12.6 s
3/100
10%
Value3,230 ms
2/100
30%
Value0.104
88/100
15%
Value16.9 s
5/100
10%
1647 ms
660 ms
890 ms
455 ms
460 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 80% of them (52 requests) were addressed to the original Island.lk, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Island.lk.
Page size can be reduced by 274.8 kB (43%)
646.0 kB
371.3 kB
In fact, the total size of Island.lk main page is 646.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. 30% of websites need less resources to load. Images take 361.9 kB which makes up the majority of the site volume.
Potential reduce by 49.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 16.4 kB, which is 27% 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 49.6 kB or 82% of the original size.
Potential reduce by 67.7 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, Island needs image optimization as it can save up to 67.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 114.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 114.1 kB or 67% of the original size.
Potential reduce by 43.4 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. Island.lk needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 83% of the original size.
Number of requests can be reduced by 28 (44%)
63
35
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Island. 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 7 to 1 for CSS and as a result speed up the page load time.
island.lk
1647 ms
script.js
660 ms
jquery.js
890 ms
cli_template.js
455 ms
module_jscript.js
460 ms
module_jscript.js
470 ms
module_jscript.js
670 ms
module_jscript.js
684 ms
main.css
688 ms
main.css
705 ms
module_css.css
880 ms
module_css.css
906 ms
module_css.css
910 ms
module_css.css
914 ms
jcarousellite_1.0.1.pack.js
741 ms
pikachoose.js
884 ms
jquery.lightbox-0.5.js
893 ms
jquery.lightbox-0.5.css
904 ms
jquery.flow.1.2.auto.js
920 ms
ga.js
21 ms
80 ms
islandbg.jpg
243 ms
advertiseTOP.jpg
259 ms
island.gif
405 ms
island_epaper.png
642 ms
prv.gif
432 ms
next.gif
450 ms
21091456677058p1-1.jpg
457 ms
1411903562p16-1.jpg
501 ms
1411675fea7-1.jpg
636 ms
1411479545b1-1.jpg
660 ms
nav_logo13.png
684 ms
hdrSearchArrow.gif
686 ms
1411669589fea6-1.jpg
737 ms
1411675fea7-1.jpg
849 ms
1411688907fea11-1.jpg
857 ms
1411695786fea10-1.jpg
887 ms
1411704117fea11-3.jpg
1141 ms
1456668953cart.jpg
916 ms
marriage1.gif
968 ms
Island-150.gif
1286 ms
defence140.jpg
1075 ms
Star-Trek.jpg
1111 ms
epal.jpg
1144 ms
stock.jpg
1200 ms
photos.gif
1296 ms
divaina100.jpg
1335 ms
navaliya100.jpg
1365 ms
vidu100.jpg
1371 ms
upali_group_logo.png
1432 ms
wait26trans.gif
1502 ms
__utm.gif
21 ms
verticalbg8.jpg
1487 ms
verticalbg2.jpg
1519 ms
verticalbg6.jpg
1422 ms
server.jsp
89 ms
cloudflare.min.js
9 ms
1400827912387.jpg
170 ms
conversion.js
28 ms
33 ms
fbds.js
89 ms
43 ms
23 ms
4 ms
nr-885.min.js
17 ms
island.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
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
Form elements do not have associated labels
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
[id] attributes on active, focusable elements are not unique
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>).
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.
island.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
island.lk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Island.lk 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 Island.lk 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.
island.lk
Open Graph description is not detected on the main page of Island. 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: