6.4 sec in total
132 ms
5.3 sec
1 sec
Click here to check amazing Critco content for Sri Lanka. Otherwise, check out these important facts you probably never knew about critco.net
Ecofriendly Packaging Solutions in Sri Lanka - Discover how our Bagasse & Paper packaging & Wooden Products can help you be sustainable.
Visit critco.netWe analyzed Critco.net page load time and found that the first response time was 132 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
critco.net performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value36.9 s
0/100
25%
Value23.0 s
0/100
10%
Value9,900 ms
0/100
30%
Value0.193
64/100
15%
Value34.3 s
0/100
10%
132 ms
2230 ms
58 ms
433 ms
200 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Critco.net, 86% (84 requests) were made to Critco.lk and 7% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Critco.lk.
Page size can be reduced by 1.2 MB (21%)
5.4 MB
4.3 MB
In fact, the total size of Critco.net main page is 5.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. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 128.9 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 24.6 kB, which is 17% 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 128.9 kB or 87% of the original size.
Potential reduce by 431.6 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. Critco images are well optimized though.
Potential reduce by 206.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 206.1 kB or 67% of the original size.
Potential reduce by 387.0 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. Critco.net needs all CSS files to be minified and compressed as it can save up to 387.0 kB or 83% of the original size.
Number of requests can be reduced by 48 (56%)
86
38
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Critco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
critco.net
132 ms
critco.lk
2230 ms
css2
58 ms
theme.css
433 ms
pe-icon-7-stroke.css
200 ms
settings.css
246 ms
front.css
200 ms
front.css
201 ms
front.css
200 ms
front.css
308 ms
frontend.min.css
328 ms
front.css
325 ms
front.css
263 ms
front.css
308 ms
custom_s_1.css
392 ms
front.css
370 ms
front.css
371 ms
ph_simpleblog-17.css
377 ms
custom.css
377 ms
front.css
512 ms
custom_s_1.css
424 ms
iqitmegamenu_s_1.css
441 ms
font-awesome.css
501 ms
custom.css
442 ms
js
60 ms
core.js
610 ms
theme.js
778 ms
front.js
480 ms
ps_shoppingcart.js
483 ms
front.js
604 ms
front.js
605 ms
instagramLite.min.js
606 ms
jquery-numerator.min.js
607 ms
frontend.js
613 ms
front.js
613 ms
front.js
660 ms
custom_s_1.js
660 ms
front.js
660 ms
front.js
778 ms
ph_simpleblog-17.js
856 ms
custom.js
718 ms
jquery.themepunch.tools.min.js
820 ms
jquery.themepunch.revolution.min.js
755 ms
css2
13 ms
callt.png
323 ms
1077086tb.png
322 ms
560463tb.png
439 ms
critco-logo-1662717290.jpg
438 ms
BIG%20(1).png
666 ms
8.8.png
666 ms
discount.jpg
663 ms
bakery%20banner.jpg
664 ms
NEW%20MODIFY.png
657 ms
1.jpg
1394 ms
GALLE.jpg
661 ms
2.jpg
669 ms
banner2.jpg
666 ms
recycle.jpg
688 ms
food.jpg
681 ms
health.jpg
684 ms
janitorial.jpg
685 ms
hyjin.jpg
736 ms
cup-cake-box-20-x-1.jpg
746 ms
plates_1.jpg
688 ms
cupss.jpg
689 ms
containers.jpg
690 ms
spoon.jpg
744 ms
payments.png
747 ms
KFOmCnqEu92Fr1Me5Q.ttf
168 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
249 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
278 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
277 ms
fontawesome-webfont.woff
745 ms
critco.lk
2223 ms
add-to-basket.png
710 ms
bg1.jpg
751 ms
instagram.png
758 ms
analytics.js
233 ms
fast-delivery.png
644 ms
payment-method.png
647 ms
ieVl2ZhZI2eCN5jzbjEETS9weq8-59U.ttf
48 ms
ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZKCM.ttf
67 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
68 ms
collect
226 ms
revolution.extension.carousel.min.js
427 ms
revolution.extension.video.min.js
435 ms
revolution.extension.slideanims.min.js
432 ms
revolution.extension.actions.min.js
435 ms
revolution.extension.layeranimation.min.js
488 ms
revolution.extension.kenburn.min.js
499 ms
revolution.extension.navigation.min.js
494 ms
revolution.extension.migration.min.js
497 ms
revolution.extension.parallax.min.js
550 ms
122 ms
coloredbg.png
66 ms
gridtile.png
66 ms
loader.gif
80 ms
revicons.woff
66 ms
critco.net accessibility score
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
Links do not have a discernible name
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.
critco.net 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
Browser errors were logged to the console
Page has valid source maps
critco.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Critco.net 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 Critco.net 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.
critco.net
Open Graph data is detected on the main page of Critco. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: