5.7 sec in total
385 ms
4.3 sec
988 ms
Visit devday.lk now to see the best up-to-date Devday content for Sri Lanka and also check out these interesting facts you probably never knew about devday.lk
2022 DEV DAY 3 Days 10 Speakers Virtual Conference 08th 09th 10th November 2022 00Days 00Hours 00Minutes 00Seconds About Conference Welcome to DEV DAY Digital Conference 2022 Rekindle the Digital Rena...
Visit devday.lkWe analyzed Devday.lk page load time and found that the first response time was 385 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
devday.lk performance score
name
value
score
weighting
Value24.3 s
0/100
10%
Value41.2 s
0/100
25%
Value87.7 s
0/100
10%
Value29,750 ms
0/100
30%
Value0.005
100/100
15%
Value94.2 s
0/100
10%
385 ms
219 ms
227 ms
202 ms
204 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 84% of them (98 requests) were addressed to the original Devday.lk, 7% (8 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Devday.lk.
Page size can be reduced by 1.6 MB (70%)
2.4 MB
707.2 kB
In fact, the total size of Devday.lk main page is 2.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. 80% 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. HTML takes 1.6 MB which makes up the majority of the site volume.
Potential reduce by 1.5 MB
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 1.5 MB or 91% of the original size.
Potential reduce by 74.5 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, Devday needs image optimization as it can save up to 74.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 10.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. This website has mostly compressed JavaScripts.
Potential reduce by 59.1 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. Devday.lk needs all CSS files to be minified and compressed as it can save up to 59.1 kB or 30% of the original size.
Number of requests can be reduced by 88 (86%)
102
14
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Devday. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
www.devday.lk
385 ms
wp-emoji-release.min.js
219 ms
style.min.css
227 ms
cookie-law-info-public.css
202 ms
cookie-law-info-gdpr.css
204 ms
niche-frame.css
220 ms
font-awesome.min.css
272 ms
animate.min.css
311 ms
themify-icons.min.css
304 ms
linea.min.css
315 ms
magnific-popup.min.css
313 ms
owl.carousel.min.css
332 ms
juxtapose.css
375 ms
styles.css
511 ms
responsive.css
417 ms
framework.css
493 ms
components.css
487 ms
responsive.css
489 ms
layers-icons.css
479 ms
layers-pro.css
522 ms
elementor-icons.min.css
878 ms
frontend-lite.min.css
677 ms
frontend-lite.min.css
571 ms
all.min.css
955 ms
v4-shims.min.css
783 ms
general.min.css
580 ms
style.css
659 ms
css
43 ms
fontawesome.min.css
865 ms
solid.min.css
826 ms
brands.min.css
859 ms
regular.min.css
918 ms
jquery.min.js
975 ms
cookie-law-info-public.js
1053 ms
plugins.js
1034 ms
layers.framework.js
973 ms
layers-pro.js
1026 ms
widget-nav-menu.min.css
459 ms
widget-animated-headline.min.css
385 ms
widget-icon-list.min.css
405 ms
cookie-law-info-table.css
852 ms
reading-progress.min.css
1582 ms
scroll-to-top.min.css
858 ms
animations.min.css
1542 ms
v4-shims.min.js
854 ms
imagesloaded.min.js
1487 ms
jquery.magnific-popup.min.js
1488 ms
juxtapose.js
1487 ms
typed.min.js
1481 ms
owl.carousel.min.js
1492 ms
jquery.countdown.min.js
1397 ms
jquery.matchHeight.min.js
1332 ms
isotope.min.js
1377 ms
packery-mode.pkgd.min.js
1460 ms
theia-sticky-sidebar.min.js
1457 ms
scripts.js
1428 ms
general.min.js
1428 ms
eael-3173.js
1368 ms
smush-lazy-load.min.js
1417 ms
jquery.smartmenus.min.js
1515 ms
eael-4577.js
1504 ms
eael-4494.js
1495 ms
eael-4525.js
1428 ms
eael-4528.js
1414 ms
eael-4531.js
1300 ms
eael-4541.js
1397 ms
eael-4544.js
1369 ms
eael-4547.js
1364 ms
reading-progress.min.js
1358 ms
scroll-to-top.min.js
1304 ms
webpack-pro.runtime.min.js
1253 ms
webpack.runtime.min.js
1414 ms
frontend-modules.min.js
1414 ms
regenerator-runtime.min.js
1402 ms
wp-polyfill.min.js
1392 ms
hooks.min.js
1384 ms
i18n.min.js
1371 ms
frontend.min.js
1503 ms
gtm.js
755 ms
speaker_bg.png
788 ms
wave_header.svg
907 ms
waypoints.min.js
758 ms
core.min.js
792 ms
frontend.min.js
754 ms
elements-handlers.min.js
753 ms
jquery.sticky.min.js
787 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uw.ttf
202 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uw.ttf
297 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uw.ttf
429 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uw.ttf
430 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uw.ttf
430 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0Uw.ttf
436 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0Uw.ttf
437 ms
N0bM2S5CPO5oOQqvazoRRb-8-MfWQZE.ttf
440 ms
naevents-elementor.js
906 ms
Chart.min.js
941 ms
lazyload.min.js
1072 ms
Helvetica.ttf
1070 ms
HelveticaLt.ttf
1069 ms
helvetica_bold1.ttf
1046 ms
fa-brands-400.woff
988 ms
fa-solid-900.woff
1078 ms
fa-regular-400.woff
1129 ms
Devday-banner-scaled.jpg
1276 ms
analytics.js
506 ms
insight.min.js
556 ms
fbevents.js
555 ms
section_02.jpg
451 ms
cocbg.png
248 ms
Footer-curve.png
606 ms
devday-2022-1-prm52bv6316o5rd4udoehf2097sdiwoei89roazocg.png
960 ms
hosting-partner-logo-pd1grwpkrvzlt7yk8gsjo3r310vh7mhb5ixaobruv4.png
960 ms
Register-Now-1.png
967 ms
collect
164 ms
922744378338604
252 ms
collect
225 ms
26 ms
devday.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
[role]s are not contained by their required parent element
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
devday.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
Browser errors were logged to the console
Page has valid source maps
devday.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Devday.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 Devday.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.
devday.lk
Open Graph data is detected on the main page of Devday. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: