87.4 sec in total
144 ms
77.3 sec
10 sec
Click here to check amazing Lotus content for Thailand. Otherwise, check out these important facts you probably never knew about lotus.com
HCLSoftware Site
Visit lotus.comWe analyzed Lotus.com page load time and found that the first response time was 144 ms and then it took 87.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 19 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lotus.com performance score
name
value
score
weighting
Value10.8 s
0/100
10%
Value12.4 s
0/100
25%
Value10.8 s
6/100
10%
Value400 ms
68/100
30%
Value0.069
96/100
15%
Value19.9 s
2/100
10%
144 ms
3978 ms
1096 ms
455 ms
3153 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lotus.com, 13% (16 requests) were made to 1.www.s81c.com and 13% (16 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (24.3 sec) relates to the external source Visitor-service-us-east-1.tealiumiq.com.
Page size can be reduced by 4.7 MB (69%)
6.8 MB
2.1 MB
In fact, the total size of Lotus.com main page is 6.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. 70% of websites need less resources to load. Javascripts take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 45.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. 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 45.2 kB or 79% of the original size.
Potential reduce by 78.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. Lotus images are well optimized though.
Potential reduce by 4.1 MB
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 4.1 MB or 77% of the original size.
Potential reduce by 423.9 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. Lotus.com needs all CSS files to be minified and compressed as it can save up to 423.9 kB or 83% of the original size.
Number of requests can be reduced by 70 (74%)
95
25
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lotus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
lotus.com
144 ms
3978 ms
1096 ms
ida_stats.js
455 ms
www.css
3153 ms
syntaxhighlighter.css
4787 ms
tables.css
3902 ms
forms.css
4247 ms
social.css
4776 ms
main-style6.css
409 ms
www.js
5062 ms
syntaxhighlighter.js
3860 ms
tables.js
5061 ms
dyntabs.js
4466 ms
forms.js
9402 ms
mustache.js
9402 ms
swg-global.js
383 ms
swg-global.css
624 ms
lpdyn-common.js
2166 ms
utag.js
386 ms
watermark.js
3313 ms
bmaid
3059 ms
lpdyn-common.js
307 ms
p_c2c3e8400272a4f619551c7d9ed6e76b811856bd88b1917cd86104495afc8607.js
157 ms
ff314b74-7164-4286-b061-d67591c3602e
5262 ms
4190 ms
search.svg
2686 ms
3_legend.png
2526 ms
IBM_verse-460x250.jpg
2311 ms
IBM_connections-460x250.jpg
2252 ms
168_300x50.jpg
3149 ms
5000-300x60.jpg
3152 ms
gartner.gif
3151 ms
forrester.png
3152 ms
mwd.png
3149 ms
usen.js
2199 ms
3315 ms
usen-utf8.js
2851 ms
utag.53.js
2227 ms
utag.44.js
2775 ms
utag.46.js
2821 ms
utag.45.js
2842 ms
utag.94.js
2841 ms
iframe_api
2519 ms
collaboration_leadspace_-buffer2000x500.jpg
1497 ms
icons-ibm-v10.svg
340 ms
icons-ibm-v10.woff
340 ms
collaboration_leadspace_-buffer2000x500.jpg
1038 ms
atrk.js
2591 ms
utag.v.js
1641 ms
social.js
8428 ms
eluminate.js
14342 ms
utag.20.js
5480 ms
utag.16.js
5565 ms
utag.3.js
5479 ms
utag.27.js
5564 ms
utag.6.js
5459 ms
utag.15.js
6319 ms
utag.19.js
6319 ms
cc.js
16120 ms
utag.52.js
6316 ms
i.gif
16976 ms
i.gif
16751 ms
i.gif
17020 ms
i.gif
16679 ms
www-widgetapi.js
19457 ms
notice
16852 ms
maxresdefault.jpg
13888 ms
videos
12723 ms
atrk.gif
13674 ms
live.js
13576 ms
conversion_async.js
13510 ms
up_loader.1.1.0.js
13509 ms
ebOneTag.js
13508 ms
insight.min.js
12836 ms
hotjar-42920.js
17315 ms
a2972860641.html
10268 ms
50200000.js
3420 ms
52640000.js
4430 ms
cm
7775 ms
015e52b302880031ee776fc37aa80006d002606500720
7148 ms
015e52b302880031ee776fc37aa80006d002606500720
24333 ms
cookie-id.js
23691 ms
dispatcher-v3.js
23645 ms
015e52b302880031ee776fc37aa80006d002606500720
23645 ms
015e52b302880031ee776fc37aa80006d002606500720
23596 ms
tpid=f93c59af-c57c-4400-bd50-ce8f18233988
23564 ms
get
2447 ms
pixel.mathtag.com
22859 ms
cm
21600 ms
cm
21600 ms
cm
21600 ms
getuid
21302 ms
oct.js
21130 ms
hit
20954 ms
get
1854 ms
Serving
20807 ms
up
0 ms
20376 ms
generic
0 ms
20288 ms
i.js
20073 ms
generic
19338 ms
rt=ifr
19184 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
4618 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
4578 ms
tpid=f93c59af-c57c-4400-bd50-ce8f18233988
1457 ms
universal_pixel.1.1.1.js
1377 ms
i.gif
3511 ms
g.json
5368 ms
tpid=
6739 ms
5907
7148 ms
visit-data
1275 ms
tpid=32470922938431113050790316796073697817
605 ms
generic
546 ms
tpid=cee800c4-b21f-45d0-9100-665f58d6372b
545 ms
appnexus
470 ms
liveramp_sync.xgi
514 ms
ibs:dpid=903&dpuuid=fcaf4652-0720-4ed6-b290-910132081deb
292 ms
rubicon
256 ms
tap.php
22 ms
liveramp_sync.xgi
157 ms
visit-data
604 ms
163 ms
lotus.com 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
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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
lotus.com 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
lotus.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lotus.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 Lotus.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.
lotus.com
Open Graph description is not detected on the main page of Lotus. 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: