2.1 sec in total
97 ms
1.6 sec
392 ms
Welcome to lotusphere.com homepage info - get ready to check Lotusphere best content right away, or after learning these important things about lotusphere.com
The place to shop for software, hardware and services from IBM and our providers. Browse by technologies, business needs and services.
Visit lotusphere.comWe analyzed Lotusphere.com page load time and found that the first response time was 97 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
lotusphere.com performance score
name
value
score
weighting
Value21.4 s
0/100
10%
Value24.3 s
0/100
25%
Value25.7 s
0/100
10%
Value12,550 ms
0/100
30%
Value0.002
100/100
15%
Value40.3 s
0/100
10%
97 ms
205 ms
96 ms
35 ms
19 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lotusphere.com, 21% (17 requests) were made to Tags.tiqcdn.com and 20% (16 requests) were made to 1.www.s81c.com. The less responsive or slowest element that took the longest time to load (246 ms) relates to the external source Consent.truste.com.
Page size can be reduced by 2.2 MB (60%)
3.6 MB
1.4 MB
In fact, the total size of Lotusphere.com main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 42.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 42.3 kB or 79% of the original size.
Potential reduce by 34.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. Lotusphere images are well optimized though.
Potential reduce by 1.9 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 1.9 MB or 79% of the original size.
Potential reduce by 206.1 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. Lotusphere.com needs all CSS files to be minified and compressed as it can save up to 206.1 kB or 84% of the original size.
Number of requests can be reduced by 58 (81%)
72
14
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lotusphere. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
lotusphere.com
97 ms
lotusphere
205 ms
lotusphere
96 ms
lotusphere
35 ms
19 ms
connect
21 ms
31 ms
ida_stats.js
31 ms
www.css
91 ms
syntaxhighlighter.css
86 ms
tables.css
88 ms
forms.css
86 ms
social.css
86 ms
main-style6.css
19 ms
www.js
151 ms
syntaxhighlighter.js
98 ms
tables.js
99 ms
dyntabs.js
99 ms
forms.js
97 ms
mustache.js
97 ms
swg-global.js
29 ms
swg-global.css
23 ms
lpdyn-common.js
7 ms
lpdyn-common.js
23 ms
utag.js
12 ms
utag.2174.js
19 ms
connect_leadspace.jpg
183 ms
utag.1230.js
84 ms
utag.695.js
81 ms
utag.700.js
83 ms
utag.753.js
83 ms
utag.764.js
83 ms
utag.805.js
82 ms
utag.1173.js
82 ms
utag.1196.js
84 ms
utag.1200.js
85 ms
utag.1261.js
84 ms
utag.1278.js
85 ms
utag.1175.js
84 ms
utag.2042.js
84 ms
utag.2165.js
172 ms
usen.js
67 ms
216 ms
notice
213 ms
usen-utf8.js
64 ms
mmcore.js
151 ms
search.svg
105 ms
connect_ibmgo_feature.png
162 ms
connect_speaker_jason.png
160 ms
connect_speaker_erik.png
165 ms
connect_go.jpg
161 ms
universal-full-bleed.jpg
231 ms
hni-v2-roman.woff
102 ms
icons-ibm-v4.svg
232 ms
icons-ibm-v4.woff
162 ms
eluminate.js
103 ms
generic
14 ms
i.gif
180 ms
generic
53 ms
i.gif
72 ms
utag.1245.js
44 ms
i.gif
83 ms
i.gif
77 ms
mmcore_old.js
22 ms
get
246 ms
50200000.js
45 ms
cm
88 ms
generic
34 ms
24 ms
cookie-id.js
128 ms
dispatcher-v3.js
47 ms
01538930711b00205318d9c696f200030003c02800720
19 ms
01538930711b00205318d9c696f200030003c02800720
18 ms
01538930711b00205318d9c696f200030003c02800720
15 ms
yahoo-min.js
109 ms
cp-v3.js
32 ms
i.js
5 ms
json-min.js
33 ms
get
84 ms
cm
44 ms
cm
45 ms
deploy2.asp
191 ms
lotusphere.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
[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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
lotusphere.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lotusphere.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lotusphere.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 Lotusphere.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.
lotusphere.com
Open Graph description is not detected on the main page of Lotusphere. 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: