3 sec in total
244 ms
2.4 sec
362 ms
Click here to check amazing Liferay content for India. Otherwise, check out these important facts you probably never knew about liferay.com
Build the digital solutions you need on the world’s most flexible digital experience platform. Learn more.
Visit liferay.comWe analyzed Liferay.com page load time and found that the first response time was 244 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.
liferay.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.6 s
1/100
25%
Value7.4 s
28/100
10%
Value2,470 ms
4/100
30%
Value0.315
37/100
15%
Value17.0 s
5/100
10%
244 ms
946 ms
58 ms
170 ms
140 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 40% of them (25 requests) were addressed to the original Liferay.com, 21% (13 requests) were made to Cdn.www.liferay.com and 8% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (946 ms) belongs to the original domain Liferay.com.
Page size can be reduced by 1.3 MB (61%)
2.1 MB
838.2 kB
In fact, the total size of Liferay.com main page is 2.1 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 962.8 kB which makes up the majority of the site volume.
Potential reduce by 95.6 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 95.6 kB or 79% of the original size.
Potential reduce by 5.5 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. Liferay images are well optimized though.
Potential reduce by 638.0 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 638.0 kB or 66% of the original size.
Potential reduce by 570.4 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. Liferay.com needs all CSS files to be minified and compressed as it can save up to 570.4 kB or 85% of the original size.
Number of requests can be reduced by 29 (52%)
56
27
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liferay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
liferay.com
244 ms
www.liferay.com
946 ms
see0ypk.js
58 ms
main.css
170 ms
main.css
140 ms
barebone.jsp
214 ms
main.css
184 ms
event-onscreen.js
137 ms
d
211 ms
main.js
81 ms
heading.png
27 ms
enterprise-ready.svg
182 ms
enterprise-ready.png
206 ms
lightweight-agile.svg
189 ms
lightweight.png
244 ms
complete-platform.svg
261 ms
platform.png
265 ms
open-source.svg
284 ms
open-source.png
295 ms
compatible.svg
310 ms
compatible.png
357 ms
integration.svg
370 ms
integration.png
357 ms
gtm.js
57 ms
28 ms
46 ms
search_icons.svg
112 ms
menu_icon.svg
114 ms
05e332db-e599-40fb-a2a4-fa1a4f0e22e0
674 ms
BjCQBBJJIpkUUkkzctMZzBCG8u+kf8YVfySLcmz9VBlflCOMPzJGOcp+qow0ePwDNNDLeQ==
95 ms
AM00Mt5
94 ms
BjCQBBJJIpkUUkkzctMZzBCG8u+kf8YVfySLcmz9VBlflCOMPzJGOcp+qow0ePwDNNDLeQ==
92 ms
AM00Mt5
91 ms
loading_animation.gif
212 ms
cta-background-1200x800.jpg
479 ms
analytics.js
67 ms
conversion_async.js
18 ms
ga.js
85 ms
2766.js
9 ms
liferay_logo_tagline.png
327 ms
search_icons.svg
375 ms
hamburger_new
397 ms
social_icons_21x21.svg
56 ms
72 ms
252686.js
107 ms
di.js
185 ms
p.gif
145 ms
collect
92 ms
collect
37 ms
__utm.gif
66 ms
122 ms
ccc97a49-26ec-42a8-bf25-82ba32622d09
268 ms
fad62970-2f68-4602-86e8-e0fa2ba58c63
292 ms
437efe46-d945-4c74-a2ef-a03d68a97eb6
339 ms
7b78d6aa-790f-4520-ad85-cd632c59ef40
352 ms
gartner-logo.svg
361 ms
collect
18 ms
all.js
158 ms
nr-476.min.js
17 ms
__ptq.gif
15 ms
__ptq.gif
8 ms
daa45428d9
82 ms
liferay.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
liferay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
liferay.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liferay.com 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 Liferay.com 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.
liferay.com
Open Graph data is detected on the main page of Liferay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: