45.4 sec in total
496 ms
43.2 sec
1.8 sec
Visit hndit.lk now to see the best up-to-date HNDIT content for Sri Lanka and also check out these interesting facts you probably never knew about hndit.lk
Higher National Diploma in Information Technology (HNDIT) Exemptions from the other academic or Professional program : B. Sc. in Software Engineering and Information Technology – Open University of Sr...
Visit hndit.lkWe analyzed Hndit.lk page load time and found that the first response time was 496 ms and then it took 45 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 13 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
hndit.lk performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.7 s
0/100
25%
Value10.2 s
8/100
10%
Value680 ms
43/100
30%
Value0.189
65/100
15%
Value15.2 s
7/100
10%
496 ms
252 ms
266 ms
296 ms
294 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 40% of them (40 requests) were addressed to the original Hndit.lk, 24% (24 requests) were made to Google.com and 13% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Hndit.lk.
Page size can be reduced by 813.0 kB (66%)
1.2 MB
410.3 kB
In fact, the total size of Hndit.lk main page is 1.2 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. 55% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 22.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 7.8 kB, which is 29% 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 22.1 kB or 82% of the original size.
Potential reduce by 49.0 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, HNDIT needs image optimization as it can save up to 49.0 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 715.3 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 715.3 kB or 69% of the original size.
Potential reduce by 26.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. Hndit.lk needs all CSS files to be minified and compressed as it can save up to 26.6 kB or 82% of the original size.
Number of requests can be reduced by 26 (34%)
76
50
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HNDIT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hndit.lk
496 ms
components.css
252 ms
responsee.css
266 ms
owl.carousel.css
296 ms
owl.theme.css
294 ms
template-style.css
299 ms
css
394 ms
jquery-1.8.3.min.js
1953 ms
jquery-ui.min.js
2781 ms
modernizr.js
1101 ms
responsee.js
456 ms
template-scripts.js
459 ms
owl.carousel.js
638 ms
analytics.js
559 ms
logo.png
298 ms
first.jpg
19902 ms
second.jpg
18140 ms
third.jpg
19902 ms
icone1.png
1452 ms
icone2.png
1445 ms
icone3.png
1444 ms
icone4.png
1723 ms
about.jpg
19745 ms
i1.jpg
2266 ms
i2.jpg
5527 ms
i3.jpg
3581 ms
i4.jpg
7787 ms
s1.jpg
10442 ms
s2.jpg
12183 ms
s3.jpg
13772 ms
s4.jpg
16750 ms
a1.jpg
19883 ms
A2.jpg
19883 ms
a3.jpg
19883 ms
a4.jpg
19884 ms
m1.jpg
19883 ms
m2.jpg
19883 ms
m3.jpg
19883 ms
m4.jpg
19883 ms
contact.jpg
19883 ms
maps
1389 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
481 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
685 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
602 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
601 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
600 ms
mfglabsiconset-webfont.svg
19754 ms
collect
75 ms
embed
881 ms
js
607 ms
init_embed.js
667 ms
common.js
276 ms
map.js
363 ms
google4.png
198 ms
overlay.js
173 ms
util.js
448 ms
onion.js
447 ms
search_impl.js
448 ms
stats.js
317 ms
openhand_8_8.cur
280 ms
ViewportInfoService.GetViewportInfo
257 ms
ViewportInfoService.GetViewportInfo
136 ms
kh
431 ms
kh
560 ms
transparent.png
308 ms
controls.js
296 ms
vt
285 ms
vt
386 ms
vt
630 ms
vt
352 ms
vt
412 ms
vt
403 ms
vt
350 ms
vt
433 ms
vt
440 ms
vt
449 ms
vt
512 ms
vt
517 ms
vt
626 ms
vt
627 ms
vt
631 ms
vt
634 ms
vt
652 ms
vt
662 ms
vt
646 ms
vt
647 ms
vt
647 ms
vt
674 ms
vt
711 ms
css
331 ms
entity11.png
151 ms
mapcnt6.png
72 ms
tmapctrl.png
118 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
637 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
784 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
1111 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
1100 ms
AuthenticationService.Authenticate
76 ms
QuotaService.RecordEvent
62 ms
mfglabsiconset-webfont.woff
19969 ms
hndit.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 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.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
hndit.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
hndit.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hndit.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 Hndit.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.
hndit.lk
Open Graph data is detected on the main page of HNDIT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: