3.6 sec in total
215 ms
2.7 sec
645 ms
Click here to check amazing LORENZ content for Germany. Otherwise, check out these important facts you probably never knew about lorenz.cc
The specialist for Regulatory Information Management solutions geared towards industry, health authorities and academia since 1989!
Visit lorenz.ccWe analyzed Lorenz.cc page load time and found that the first response time was 215 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lorenz.cc performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value11.5 s
0/100
25%
Value6.4 s
41/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value7.4 s
48/100
10%
215 ms
679 ms
725 ms
572 ms
482 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 98% of them (43 requests) were addressed to the original Lorenz.cc, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lorenz.cc.
Page size can be reduced by 779.1 kB (21%)
3.7 MB
2.9 MB
In fact, the total size of Lorenz.cc main page is 3.7 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. 35% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 48.2 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 19.0 kB, which is 35% 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 48.2 kB or 88% of the original size.
Potential reduce by 393.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, LORENZ needs image optimization as it can save up to 393.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 125.4 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 125.4 kB or 57% of the original size.
Potential reduce by 212.5 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. Lorenz.cc needs all CSS files to be minified and compressed as it can save up to 212.5 kB or 84% of the original size.
Number of requests can be reduced by 9 (22%)
41
32
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LORENZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lorenz.cc
215 ms
lorenz.cc
679 ms
bootstrap.min.css
725 ms
style.css
572 ms
font-awesome.min.css
482 ms
klaro.css
400 ms
klaro_config.js
400 ms
klaro-no-css.js
487 ms
js
63 ms
jquery.min.js
494 ms
popper.min.js
317 ms
bootstrap.min.js
483 ms
custom.js
405 ms
24_Webpage_Banner_Background-Converge.png
868 ms
24_Webpage_Banner_Logo-Converge.png
707 ms
24-PI-View-Website_Banner_background.png
796 ms
24-PI-View-symbol-for-banner.png
627 ms
23_Homepage_Banner_RIM_Background-1920px.png
1067 ms
rimgif.gif
456 ms
Submission_Management_Icon_Green.png
544 ms
docuBridge_Product_Icon.png
632 ms
Document_Management_Icon_Green.png
714 ms
Submission_Validation_Icon_Lightblue.png
720 ms
eValidator_Product_Icon.png
794 ms
Product_Information_Management_Icon_Darkblue.png
803 ms
drugTrack_Product_Icon.png
809 ms
Product_Lifecycle_Management_Icon_Darkblue.png
879 ms
Business_Automation_Icon_Lightblue.png
881 ms
Automator_Product_Icon.png
892 ms
Regulatory_Information_Management_Icon.png
896 ms
Placeholder_Icon.png
948 ms
World_Map_Website_customers.png
1224 ms
World-map-authorities.png
1142 ms
lorenz_life_sciences_group_logo_sml.png
89 ms
closeMenue.png
88 ms
lorenz_life_sciences_group_logo.png
89 ms
bg_70opacity_wt.png
87 ms
wavylines.png
87 ms
footer-LinkedIn-Icon.png
90 ms
footer_docuBridge_ShowcasePage.png
174 ms
footer_drugTrack_ShowcasePage.png
175 ms
footer_docuBridgeONE_Group.png
179 ms
footer_eValidator_Basic_Group.png
179 ms
fontawesome-webfont.woff
189 ms
lorenz.cc 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
lorenz.cc 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
lorenz.cc SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lorenz.cc 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 Lorenz.cc 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.
lorenz.cc
Open Graph description is not detected on the main page of LORENZ. 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: