10.7 sec in total
2.3 sec
8.1 sec
291 ms
Visit lr.co.za now to see the best up-to-date Lr content for South Africa and also check out these interesting facts you probably never knew about lr.co.za
Visit lr.co.zaWe analyzed Lr.co.za page load time and found that the first response time was 2.3 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Lr.co.za rating and web reputation
lr.co.za performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value9.1 s
1/100
25%
Value19.2 s
0/100
10%
Value5,020 ms
0/100
30%
Value0.023
100/100
15%
Value26.5 s
0/100
10%
2312 ms
706 ms
1171 ms
475 ms
1184 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lr.co.za, 7% (5 requests) were made to Google-analytics.com and 4% (3 requests) were made to Insights.hotjar.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Lrmg.co.za.
Page size can be reduced by 1.0 MB (67%)
1.6 MB
521.8 kB
In fact, the total size of Lr.co.za 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 154.3 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 154.3 kB or 76% of the original size.
Potential reduce by 10.0 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. Lr images are well optimized though.
Potential reduce by 746.9 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 746.9 kB or 69% of the original size.
Potential reduce by 136.7 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. Lr.co.za needs all CSS files to be minified and compressed as it can save up to 136.7 kB or 84% of the original size.
Number of requests can be reduced by 32 (48%)
66
34
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
lrmg.co.za
2312 ms
style.css
706 ms
bootstrap.min.css
1171 ms
font_styles.css
475 ms
jquery-1.11.1.min.js
1184 ms
bootstrap.min.js
709 ms
ajax.class.js
472 ms
isotope.pkgd.min.js
1203 ms
script.js
709 ms
flow.js
945 ms
modernizr.js
945 ms
initFunctions.js
945 ms
endBody.js
1241 ms
j.php
14 ms
logo.png
420 ms
menu_icon.png
421 ms
twitter.png
422 ms
facebook.png
418 ms
chat.png
421 ms
LRMG_homepage_2.jpg
421 ms
mouse_scroll.png
481 ms
icon1.png
479 ms
icon1h.png
489 ms
icon11.png
490 ms
icon11h.png
816 ms
icon4.png
489 ms
icon4h.png
713 ms
icon2.png
714 ms
icon2h.png
717 ms
icon6.png
719 ms
icon6h.png
723 ms
icon3.png
949 ms
icon3h.png
949 ms
icon10.png
950 ms
icon10h.png
1355 ms
icon5.png
956 ms
icon5h.png
1053 ms
icon9.png
1183 ms
icon9h.png
1182 ms
icon12.png
1186 ms
icon12h.png
2625 ms
logo_blue.jpg
1288 ms
gtm.js
75 ms
sdk.js
74 ms
v.gif
59 ms
drop_down_arrow.png
1398 ms
menu_bg.jpg
1399 ms
home_search_bg.png
1401 ms
widgets.js
335 ms
ga.js
123 ms
myriadpro-light-webfont.woff
1638 ms
MyriadProSemibold.woff
1939 ms
MYRIADPRO-REGULAR.woff
1878 ms
analytics.js
53 ms
conversion_async.js
54 ms
hotjar-37342.js
305 ms
prum.min.js
49 ms
addthis_widget.js
50 ms
253 ms
__utm.gif
172 ms
linkid.js
156 ms
210 ms
xd_arbiter.php
138 ms
xd_arbiter.php
184 ms
collect
23 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
61 ms
collect
117 ms
100 ms
visit-data
225 ms
b0daf430b8ffb21aaf2da19026d7b166
97 ms
content
733 ms
myriadpro-regular-webfont.ttf
1574 ms
300lo.json
37 ms
sh.8e5f85691f9aaa082472a194.html
38 ms
beacon.gif
131 ms
layers.e5ea973510bf60b3db41.js
35 ms
lr.co.za 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-hidden="true"] elements contain focusable descendents
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
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
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.
lr.co.za 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lr.co.za 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lr.co.za 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 Lr.co.za 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.
lr.co.za
Open Graph description is not detected on the main page of Lr. 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: