3.2 sec in total
356 ms
2.6 sec
210 ms
Visit cri.lu now to see the best up-to-date CRI content and also check out these interesting facts you probably never knew about cri.lu
CRI GROUP
Visit cri.luWe analyzed Cri.lu page load time and found that the first response time was 356 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
cri.lu performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0.096
91/100
15%
Value0.8 s
100/100
10%
356 ms
468 ms
24 ms
38 ms
185 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cri.lu, 85% (68 requests) were made to Cri-group.eu and 4% (3 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (640 ms) relates to the external source Cri-group.eu.
Page size can be reduced by 419.7 kB (42%)
1.0 MB
589.7 kB
In fact, the total size of Cri.lu main page is 1.0 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. 40% of websites need less resources to load. Images take 462.4 kB which makes up the majority of the site volume.
Potential reduce by 135.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. 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 135.9 kB or 69% of the original size.
Potential reduce by 25.1 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. CRI images are well optimized though.
Potential reduce by 168.5 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 168.5 kB or 68% of the original size.
Potential reduce by 90.2 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. Cri.lu needs all CSS files to be minified and compressed as it can save up to 90.2 kB or 87% of the original size.
Number of requests can be reduced by 21 (28%)
75
54
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CRI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cri.lu
356 ms
home.html
468 ms
css
24 ms
css
38 ms
normalize.css
185 ms
unsemantic-grid-responsive.css
346 ms
jquery.bxslider.css
182 ms
main.css
277 ms
jquery-jvectormap-1.2.2.css
195 ms
font-awesome.min.css
5 ms
modernizr-2.6.2.min.js
272 ms
jquery.min.js
23 ms
plugins.js
99 ms
jquery-jvectormap-1.2.2.min.js
309 ms
jquery-jvectormap-europe-mill-en.js
498 ms
jquery.easing.1.3.js
311 ms
jquery.fitvids.js
309 ms
jquery.bxslider.min.js
310 ms
main.js
312 ms
cms39_accessibility.css
340 ms
jquery.cookie.min.js
9 ms
jquery.blockUI.min.js
9 ms
jquery.simplemodal.min.js
10 ms
audio5.min.js
338 ms
cms39_accessibility.js
337 ms
favicon
131 ms
bg_top_bar.gif
120 ms
search_input_bg.png
132 ms
search_btn.png
186 ms
logo.png
192 ms
slide_home.jpg
347 ms
slide_2.jpg
344 ms
slide_3.jpg
344 ms
slide_4.jpg
339 ms
slide_5.jpg
355 ms
ico_1.png
347 ms
ico_2.png
360 ms
ico_3.png
362 ms
ico_4.png
410 ms
about-us-ico.jpg
421 ms
45_45_crop_80_0_2015121616017_cop21_web.png
439 ms
45_45_crop_80_0_2015121616010_mobilemarketingmutlimedia_web.png
447 ms
45_45_crop_80_0_2015121615044_salesforce_web.png
453 ms
45_45_crop_80_0_2015071114125_era_web.png
448 ms
45_45_crop_80_0_2015071114143_eeas_web.png
493 ms
45_45_crop_80_0_2015060318158_era_web.png
506 ms
45_45_crop_80_0_2015050415114_opac_web.jpg
529 ms
45_45_crop_80_0_2015030517041_amc_web.png
538 ms
45_45_crop_80_0_2015022612045_logo_european-parliament_web.png
535 ms
45_45_crop_80_0_2015022612040_logo_plovdiv_city_web.png
546 ms
45_45_crop_80_0_2015022612053_logo_european-commission_web.png
578 ms
45_45_crop_80_0_2015022612014_logo_ria_web.png
591 ms
45_45_crop_80_0_2015022518050_logo_mtel_web.png
560 ms
45_45_crop_80_0_2014120219035_cri-belgium_new-office_web.png
560 ms
45_45_crop_80_0_2014110413034_logo_mtel_web.png
567 ms
45_45_crop_80_0_2014110412034_eurostat_logo_web.jpg
576 ms
45_45_crop_80_0_2014110412032_logo_european-commission_web.png
598 ms
cSd7NBXNFQWK4oX1706dY6CWcynf_cDxXwCLxiixG1c.ttf
10 ms
fontawesome-webfont.woff
9 ms
Lqv9ztoTUV8Q0FmQZzPqaDZ8Xgu54OUP9A9ig-MN_aY.ttf
17 ms
45_45_crop_80_0_2014110412035_logo_european-commission_web.png
589 ms
45_45_crop_80_0_2014110413046_mobile-conf_web.png
623 ms
45_45_crop_80_0_2014110413006_logo_huawei_web.png
615 ms
45_45_crop_80_0_2014110413042_logo_vodafone_web.png
626 ms
45_45_crop_80_0_2014110413049_eurostat_logo_web.jpg
640 ms
45_45_crop_80_0_2014110413028_logo_vivacom_web.png
609 ms
45_45_crop_80_0_2014011516031_amc_ro.png
604 ms
45_45_crop_80_0_2014011515058_rcs_rds.png
628 ms
45_45_crop_80_0_2014011515055_amc_on_green-157.png
486 ms
45_45_crop_80_0_2014011610054_2014011516022_nato_nspa.jpg
493 ms
45_45_crop_80_0_2014011610021_2014011516022_eib.jpg
509 ms
45_45_crop_80_0_2014011516006_piraeusbank.png
520 ms
45_45_crop_80_0_2014011610025_2014011516019_eurostat1.jpg
516 ms
45_45_crop_80_0_2014011516032_epo.png
541 ms
bg_footer.gif
547 ms
list_hor.png
551 ms
bx_loader.gif
566 ms
slide_home.jpg
601 ms
left.png
520 ms
right.png
535 ms
cri.lu 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
cri.lu 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
cri.lu SEO score
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 Cri.lu 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 Cri.lu 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.
cri.lu
Open Graph data is detected on the main page of CRI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: