2.3 sec in total
761 ms
1.5 sec
69 ms
Click here to check amazing Docs Leanplum content for United States. Otherwise, check out these important facts you probably never knew about docs.leanplum.com
Visit docs.leanplum.comWe analyzed Docs.leanplum.com page load time and found that the first response time was 761 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
docs.leanplum.com performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value7.6 s
4/100
25%
Value7.6 s
26/100
10%
Value2,290 ms
5/100
30%
Value0
100/100
15%
Value17.1 s
4/100
10%
761 ms
47 ms
59 ms
73 ms
104 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Docs.leanplum.com, 87% (73 requests) were made to Cdn.readme.io and 4% (3 requests) were made to Storage.googleapis.com. The less responsive or slowest element that took the longest time to load (761 ms) belongs to the original domain Docs.leanplum.com.
Page size can be reduced by 935.2 kB (82%)
1.1 MB
199.8 kB
In fact, the total size of Docs.leanplum.com main page is 1.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. 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. HTML takes 995.6 kB which makes up the majority of the site volume.
Potential reduce by 909.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 909.3 kB or 91% of the original size.
Potential reduce by 21.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 21.0 kB or 16% of the original size.
Potential reduce by 4.8 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. Docs.leanplum.com needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 77% of the original size.
Number of requests can be reduced by 78 (98%)
80
2
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs Leanplum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
docs.leanplum.com
761 ms
force-firefox-anchor-jump.js
47 ms
cash-dom.min.js
59 ms
ui-styles.bfaf0efbe7aa0db7d472.css
73 ms
main.a5067f3fee859b65181a.css
104 ms
SuperHub.61f46c483fc6bca55be1.css
71 ms
6445.205f7406e520f663cc7e.css
67 ms
Header.1db27e25cc7c5239b751.css
137 ms
routes-Doc.66b638af6954c2bc41e7.css
101 ms
routes-PageNotFound.1ada8671884e2a5b981e.css
139 ms
routes-Reference.3796474981b71cebdf11.css
112 ms
CustomPage.a1623b056ecdeb4ea8ba.css
139 ms
routes-Landing.deb20a34df81597af259.css
135 ms
routes-Suggestions-ngz-Header.0f3cc7b3c9b6779eaadb.css
135 ms
Editor.aee3a1c5df91b77271a1.css
139 ms
routes-Tutorials.d504811ee21a1f3237be.css
155 ms
routes-Changelog.2143029241ae2e32eeb8.css
157 ms
Post.a1623b056ecdeb4ea8ba.css
153 ms
List.7453b58d34890a6d12bb.css
157 ms
routes-Discuss.4b7fd1bde3e01607d9c2.css
151 ms
Page.f2fce73170d5d6f02cfc.css
153 ms
New.f2fce73170d5d6f02cfc.css
159 ms
leanplum.min.js
110 ms
combined-latest-15-01-2020.js
156 ms
jquery.min.js
32 ms
mustache.min.js
180 ms
docs_15_01_newUI.css
180 ms
main.2bd202b0383a3704a4b3.js
70 ms
2458.dca973bd8d5390956721.js
33 ms
5056.bc021bc506379ab09494.js
31 ms
2711.75c9e2251fbccbc50370.js
35 ms
SuperHub.9bb89ee8ecdb050bbbe0.js
68 ms
5418.a2bd04c26797820b8dcf.js
31 ms
1725.2a088419ef5f7957bfa5.js
70 ms
3602.cac3d534d705d957037a.js
69 ms
6445.56131f3687724bdb5714.js
70 ms
Header.2617633f2e07d8c2abe0.js
80 ms
core-icons-chevron-up-down-svg.3c49fd5f594d73a19603.js
80 ms
2438.9228c93cefde9d4dca73.js
80 ms
8954.1e531ac039fe3604126f.js
81 ms
7452.1e957fdeb9667f9c939e.js
81 ms
223.deb740e669f4327440da.js
85 ms
2004.ed885f5d28d0abcc9a93.js
88 ms
119.df0640711f75db9f8611.js
95 ms
routes-Doc.eba4881983fa6934680a.js
90 ms
Footer.e4ab732e2c66f0aa96f4.js
88 ms
routes-PageNotFound.0264acc7bd2a7c7e154a.js
95 ms
1140.783c21a724fba8fd4824.js
89 ms
9963.4baea0e18aa0016e0860.js
121 ms
8872.3ec28f51ff83d3c72c9f.js
120 ms
6284.8b25a7a299f14cba2567.js
146 ms
7309.18421d26cd8fdb46eda5.js
121 ms
routes-Reference.6f8be4efa4784a5527fe.js
125 ms
core-icons-more-vertical-svg.90201a769018f8b99913.js
120 ms
5209.cc3aaa5bea8c2ac44a29.js
152 ms
CustomPage.22fe6b6265e3b75846c1.js
146 ms
element.js
79 ms
routes-Landing.a9aadf40ad0fb79247e4.js
143 ms
core-icons-arrow-right-svg.9ba256404ac5dbffac0d.js
148 ms
core-icons-arrow-up-right-svg.afaef8ffb8c4a65db9e2.js
146 ms
routes-Suggestions-ngz-Header.f122d9072be7c52e072f.js
147 ms
4695.e54c46e4418f7aacb503.js
155 ms
5778.8f7f824c276a64e8705f.js
135 ms
Editor.f803cbb0cd8f9c222946.js
137 ms
core-icons-x-circle-svg.7a602600b87b5b87962e.js
143 ms
core-icons-suggested-edits-svg.ab1cb04dee24b9e24b0f.js
139 ms
routes-Tutorials.74432a1315b766500252.js
143 ms
c88e191-small-Leanplum_Logo_White.png
110 ms
%7B%7BimageUrl%7D%7D
613 ms
analytics.js
31 ms
core-icons-chevron-down-svg.74cde732ebe855f38317.js
110 ms
routes-Changelog.f707e402580a7ee60955.js
114 ms
Post.d8a53cbc406b1e8c047d.js
115 ms
8231.c272475a3ae450cbe4dd.js
117 ms
List.ae64ca156d29d30b2404.js
121 ms
routes-Discuss.ad9940b0db1ddae0774d.js
116 ms
core-icons-trending-up-svg.76f620512ffdc648b68b.js
108 ms
core-icons-callout-info-svg.666c8357a565e8a06131.js
111 ms
core-icons-star-svg.71a50923acfcf2da593b.js
121 ms
Page.0371b8285450d4574f5d.js
118 ms
fs.js
48 ms
core-icons-key-svg.6eab33a516a85d80d460.js
116 ms
New.de6754fcb4b844f5a29b.js
122 ms
13d8dde474942669736ac81985cd072d.ttf
93 ms
docs.leanplum.com accessibility score
docs.leanplum.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
Browser errors were logged to the console
Page has valid source maps
docs.leanplum.com SEO score
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 Docs.leanplum.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 Docs.leanplum.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.
docs.leanplum.com
Open Graph description is not detected on the main page of Docs Leanplum. 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: