Access vtasl.gov.lk. 404 Page Not Found

vtasl.gov.lk screenshot

2

Performance

Renders faster than
20% of other websites
85

Accessibility

Visual factors better than
that of 58% of websites
50

Best Practices

More advanced features
available than in
19% of websites
77

SEO

Google-friendlier than
36% of websites

First Response

913 ms

Resources Loaded

6.3 sec

Page Rendered

715 ms

vtasl.gov.lk screenshot

About Website

Welcome to vtasl.gov.lk homepage info - get ready to check Vtasl best content for Sri Lanka right away, or after learning these important things about vtasl.gov.lk

VTA | Srilanka

Visit vtasl.gov.lk

Key Findings

We analyzed Vtasl.gov.lk page load time and found that the first response time was 913 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value38.6 s

0/100

25%

SI (Speed Index)

Value24.2 s

0/100

10%

TBT (Total Blocking Time)

Value3,120 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.655

8/100

15%

TTI (Time to Interactive)

Value43.0 s

0/100

10%

vtasl.gov.lk

913 ms

course.vta.lk

1369 ms

js

94 ms

sweetalert.css

197 ms

bootstrap.min.css

303 ms

Our browser made a total of 251 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Vtasl.gov.lk, 44% (111 requests) were made to Course.vta.lk and 43% (109 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Course.vta.lk.

Content Size

7.5 MB

After Optimization

6.8 MB

In fact, the total size of Vtasl.gov.lk main page is 7.5 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. Only a small number of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 333.9 kB

Original 357.7 kB
After minification 173.3 kB
After compression 23.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. This page needs HTML code to be minified as it can gain 184.4 kB, which is 52% 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 333.9 kB or 93% of the original size.

Image Optimization

-4%

Potential reduce by 236.6 kB

Original 6.1 MB
After minification 5.9 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. Vtasl images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 118.0 kB

Original 800.0 kB
After minification 757.9 kB
After compression 682.0 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 118.0 kB or 15% of the original size.

CSS Optimization

-11%

Potential reduce by 24.3 kB

Original 224.9 kB
After minification 224.9 kB
After compression 200.5 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. Vtasl.gov.lk needs all CSS files to be minified and compressed as it can save up to 24.3 kB or 11% of the original size.

Requests Now

136

After Optimization

71

The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vtasl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

robots.txt is not valid

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vtasl.gov.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 Vtasl.gov.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.

Social Sharing Optimization

vtasl.gov.lk

Open Graph description is not detected on the main page of Vtasl. 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: