13.7 sec in total
731 ms
7.8 sec
5.2 sec
Visit carl.eu now to see the best up-to-date CARL content and also check out these interesting facts you probably never knew about carl.eu
Discover the CMMS solution adapted to your business sector. Equipment-maintenance software and applications.
Visit carl.euWe analyzed Carl.eu page load time and found that the first response time was 731 ms and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
carl.eu performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.3 s
10/100
25%
Value8.1 s
21/100
10%
Value1,260 ms
19/100
30%
Value0.39
26/100
15%
Value10.6 s
23/100
10%
731 ms
295 ms
535 ms
104 ms
107 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Carl.eu, 88% (94 requests) were made to Carl-software.com and 3% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Carl-software.com.
Page size can be reduced by 131.2 kB (8%)
1.6 MB
1.5 MB
In fact, the total size of Carl.eu main page is 1.6 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 121.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 20.5 kB, which is 14% 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 121.8 kB or 85% of the original size.
Potential reduce by 9.3 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. CARL images are well optimized though.
Potential reduce by 101 B
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 0 B
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.
Number of requests can be reduced by 56 (55%)
101
45
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CARL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
carl.eu
731 ms
www.carl-software.com
295 ms
www.carl-software.com
535 ms
css
104 ms
wp-emoji-release.min.js
107 ms
style.min.css
273 ms
styles.css
264 ms
style.css
290 ms
page-list.css
290 ms
cookie-law-info-public.css
291 ms
cookie-law-info-gdpr.css
361 ms
style.min.css
353 ms
foundation.css
520 ms
foundation_complement.css
362 ms
stylesCarl.css
538 ms
stylesCarlDescode.css
374 ms
carlicons.css
442 ms
animate.css
565 ms
prettyLoader.css
449 ms
responsive_Carl.css
598 ms
style.basic.css
621 ms
style-simple-red.css
567 ms
js_composer.min.css
763 ms
jquery.min.js
743 ms
jquery-migrate.min.js
641 ms
cookie-law-info-public.js
723 ms
script.min.js
641 ms
jquery.min.js
907 ms
what-input.min.js
744 ms
foundation.min.js
1080 ms
jquery.smooth-scroll.min.js
946 ms
wow.min.js
948 ms
jquery.browser.min.js
948 ms
jquery.prettyLoader.js
948 ms
carl_scripts.js
948 ms
xdomain-data.js
952 ms
js_composer_tta.min.css
1989 ms
index.js
948 ms
index.js
950 ms
api.js
57 ms
asl-prereq.js
913 ms
asl-core.js
787 ms
asl-settings.js
752 ms
asl-results-vertical.js
775 ms
asl-autocomplete.js
1703 ms
asl-load.js
1704 ms
asl-wrapper.js
1644 ms
regenerator-runtime.min.js
1635 ms
wp-polyfill.min.js
1635 ms
index.js
1640 ms
js_composer_front.min.js
1574 ms
vc-accordion.min.js
1568 ms
vc-tta-autoplay.min.js
1484 ms
qgq7giv.css
127 ms
vc-tabs.min.js
1455 ms
lazyload.min.js
1451 ms
p.css
79 ms
logo_Berger_Levrault.png
844 ms
logo_Carlsoftware.jpg
669 ms
nav_produits.jpg
670 ms
nav_innovation.jpg
670 ms
nav_services.jpg
671 ms
nav_actu.jpg
668 ms
nav_carl.jpg
669 ms
nav_contact.jpg
694 ms
btSlide_previous.png
697 ms
btSlide_next.png
695 ms
BL-Viz4d-viewer-370x107px.jpg
693 ms
Axino-partnership-370x107px.jpg
696 ms
Gruyere-energie-370x107px.jpg
692 ms
BEP-370x107px.jpg
690 ms
Prototype-AR-370x107pxpx.jpg
690 ms
HEADER-CARLSOURCE-WEB-mini-IT.jpg
692 ms
visuel-Intro-HomePage.jpg
691 ms
visuTabs_Factory.jpg
739 ms
visuTabs_Factory_mobile.jpg
692 ms
visuTabs_Facility.jpg
692 ms
visuTabs_Facility_mobile.jpg
721 ms
visuTabs_Transport.jpg
723 ms
visuTabs_Transport_mobile.jpg
721 ms
visuTabs_Sante.jpg
721 ms
visuTabs_Sante_mobile.jpg
469 ms
visuTabs_City.jpg
542 ms
visuTabs_City_mobile.jpg
528 ms
brembo.jpg
528 ms
arcelor.jpg
527 ms
aprr.jpg
515 ms
hospiceslyon.jpg
522 ms
img_video.jpg
522 ms
picto_Facebook.gif
521 ms
picto_Twitter.gif
520 ms
logo-cookieyes.svg
520 ms
d
95 ms
d
96 ms
carlicons.ttf
470 ms
js
1085 ms
ajax-loader.gif
928 ms
FR_slider_CARLXPRESS.jpg
291 ms
FR_slider_CARL_SOURCE_V6.jpg
431 ms
FR_slider_flash.jpg
420 ms
FR_slider_CARLTOUCH.jpg
417 ms
FR_slider_CARL_BL-1.jpg
415 ms
FR_slider_PAROLES-EXPERTS.jpg
417 ms
api.js
236 ms
analytics.js
94 ms
recaptcha__en.js
231 ms
collect
319 ms
carl.eu accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
carl.eu 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
Missing source maps for large first-party JavaScript
carl.eu 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carl.eu 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 Carl.eu 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.
carl.eu
Open Graph data is detected on the main page of CARL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: