3.3 sec in total
275 ms
2.8 sec
261 ms
Welcome to lafarge.ro homepage info - get ready to check Lafarge best content for Romania right away, or after learning these important things about lafarge.ro
În calitate de lider global în soluții inovatoare și durabile specialiștii Holcim dezvoltă materiale având ca principali vectori responsabilitatea socială și față de mediu.
Visit lafarge.roWe analyzed Lafarge.ro page load time and found that the first response time was 275 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
lafarge.ro performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value14.3 s
0/100
25%
Value5.9 s
49/100
10%
Value720 ms
41/100
30%
Value0.176
69/100
15%
Value6.9 s
54/100
10%
275 ms
356 ms
158 ms
158 ms
163 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lafarge.ro, 75% (76 requests) were made to Lafargeholcim.com and 11% (11 requests) were made to F1.eu.readspeaker.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Lafargeholcim.com.
Page size can be reduced by 1.4 MB (78%)
1.8 MB
406.4 kB
In fact, the total size of Lafarge.ro main page is 1.8 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. 50% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 66.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. 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 66.8 kB or 79% 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. Obviously, Lafarge needs image optimization as it can save up to 25.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 797.2 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 797.2 kB or 78% of the original size.
Potential reduce by 515.6 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. Lafarge.ro needs all CSS files to be minified and compressed as it can save up to 515.6 kB or 87% of the original size.
Number of requests can be reduced by 80 (83%)
96
16
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lafarge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
www.lafarge.ro
275 ms
directory
356 ms
system.base.css
158 ms
jquery.ui.core.min.css
158 ms
jquery.ui.theme.min.css
163 ms
jquery.ui.menu.min.css
169 ms
jquery.ui.autocomplete.min.css
166 ms
content_type_thumbnail.css
169 ms
date.css
239 ms
datepicker.1.7.css
234 ms
editor-global.css
243 ms
entityreference_live_preview.css
246 ms
field.css
245 ms
dzsportfolio.css
411 ms
vplayer.css
462 ms
plugin.css
400 ms
node.css
324 ms
poll.css
327 ms
scald_file.css
325 ms
search.css
409 ms
user.css
407 ms
extlink.css
415 ms
views.css
483 ms
back_to_top.css
488 ms
jquery.fancybox.css
491 ms
ckeditor.css
489 ms
colorbox_style.css
494 ms
ctools.css
537 ms
interactivemap.css
564 ms
menu_icons.css
569 ms
panels.css
573 ms
pollanon.css
571 ms
meanmenu.min.css
575 ms
ReadSpeakerSampleSkin.css
612 ms
video-js.css
729 ms
styles.css
1141 ms
lh.css
898 ms
css
25 ms
ReadSpeaker.js
70 ms
print.css
589 ms
modernizr.min.js
508 ms
js_jpJjaUC0z8JMIyav5oQrYykDRUb64rpaUDpB4Y9aklU.js
614 ms
js_GnurzbirOTBbGOwBzS68QdXDEdLXtOeSs8cTiHdc-_g.js
823 ms
js_CzKW-6BmPFtgcNh43G5yHo3202eKnAJYPO9xgFXE9LA.js
581 ms
js_LJZOrmHyeEbnjDTdFkbMEwZIc4uq18k7KjxJyIMYQ5U.js
855 ms
js_PMlMwMWT3MONR7Am1koe4Xl57FTYRnX8s6PI7cminDE.js
662 ms
js_rOP2AOpyQ7SvmrW0Dq5eQsP6xJOkULlFowFBtmi6OuQ.js
614 ms
js_teNkfNfBu-QZcfml23CTq9EyIwp3210HESeaCB479nQ.js
680 ms
js_zVVh7IPmfpahCVWggdgFmN9r2qZ5urKgGCpg8LBKIoA.js
684 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
743 ms
facebook-header-icon.png
751 ms
twitter-header-icon.png
680 ms
linkedin-header-icon.png
745 ms
youtube-header-icon.png
742 ms
instagram-header-icon.png
678 ms
www.lafargeholcim.com
674 ms
lh_logo1.jpg
697 ms
lh_logotype_horizontal_srgb_horizontal_7.jpg
801 ms
search.png
802 ms
arrow-down.png
874 ms
facebook-icon.png
734 ms
twitter-icon.png
730 ms
linkedin-icon.png
850 ms
youtube-icon.png
764 ms
instagram-icon.png
761 ms
sprite-pictos.png
158 ms
sprite-pictos.png
156 ms
ReadSpeakerSampleSkin.png
159 ms
menu_icon_1418.png
160 ms
menu_icon_4488.png
194 ms
menu_icon_1423.png
194 ms
menu_icon_1425.png
194 ms
menu_icon_3665.png
195 ms
xtcore_en.js
186 ms
LeFlHvsZjXu2c3ZRgBq9nD8E0i7KZn-EPnyo3HZu7kw.woff
37 ms
PIbvSEyHEdL91QLOQRnZ13hCUOGz7vYGh680lGh-uXM.woff
37 ms
analytics.js
238 ms
ReadSpeaker.Styles.css
33 ms
ReadSpeaker.Core.js
233 ms
ReadSpeaker.pub.Config.js
234 ms
ti.js
183 ms
ui-bg_flat_75_ffffff_40x100.png
89 ms
backtotop.png
90 ms
print.png
90 ms
throbber-active.gif
91 ms
p
42 ms
axHjtYliGr5Bw9acwqm_6r.js
16 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
29 ms
linkid.js
6 ms
collect
13 ms
ReadSpeaker.Common.Settings.js
31 ms
ReadSpeaker.PlayerAPI.js
133 ms
ReadSpeaker.HL.js
122 ms
ReadSpeaker.ui.js
126 ms
v2
48 ms
hit.xiti
209 ms
dpx
9 ms
xrefid.xgi
6 ms
ca.png
166 ms
ReadSpeaker.enlargeHL.js
67 ms
ReadSpeaker.enlargeHL.css
66 ms
lafarge.ro 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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
lafarge.ro 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
lafarge.ro 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
Tap targets are not sized appropriately
RO
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lafarge.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it does not match the claimed English language. Our system also found out that Lafarge.ro 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.
lafarge.ro
Open Graph description is not detected on the main page of Lafarge. 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: