1.1 sec in total
86 ms
932 ms
57 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 86 ms and then it took 989 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
docs.leanplum.com performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value9.9 s
0/100
25%
Value9.8 s
10/100
10%
Value2,630 ms
4/100
30%
Value0.102
89/100
15%
Value22.2 s
1/100
10%
86 ms
355 ms
80 ms
80 ms
104 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Docs.leanplum.com, 86% (74 requests) were made to Cdn.readme.io and 3% (3 requests) were made to Storage.googleapis.com. The less responsive or slowest element that took the longest time to load (381 ms) belongs to the original domain Docs.leanplum.com.
Page size can be reduced by 938.3 kB (82%)
1.1 MB
211.1 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. 80% 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 999.4 kB which makes up the majority of the site volume.
Potential reduce by 912.4 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 912.4 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 15% 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 79 (98%)
81
2
The browser has sent 81 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 65 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
docs.leanplum.com
86 ms
docs.leanplum.com
355 ms
force-firefox-anchor-jump.js
80 ms
cash-dom.min.js
80 ms
ui-styles.d46c8c5fee007cb4d6aa.css
104 ms
main.aca7568da969c21d26b6.css
89 ms
7190.021ca491b0c05c581bc7.css
86 ms
routes-SuperHub.1bc74a47acc469670b6d.css
83 ms
Header.20c80e1b3fe1f87822be.css
99 ms
routes-Doc.921b58c17b447c4e783e.css
101 ms
routes-PageNotFound.d8afd1171cf7a455eed7.css
132 ms
Editor.c55904521189f643e443.css
132 ms
1068.af90773be8828cb99c94.css
130 ms
routes-Reference.1c52c057ba70042c0c1d.css
134 ms
routes-Changelog.322e76a9906b7996894b.css
134 ms
List.575af6c70506c337438a.css
138 ms
routes-Landing.c5ea43d2f4b3b926ff1f.css
135 ms
routes-Discuss.030a6503a108b6c19d2c.css
136 ms
CustomPage.38a39d6ce8b0e2afad5a.css
136 ms
leanplum.min.js
96 ms
combined-latest-15-01-2020.js
132 ms
jquery.min.js
50 ms
mustache.min.js
62 ms
docs_15_01_newUI.css
136 ms
main.0f931bcfc1e3c4e1738b.js
230 ms
8217.81dee0256f1090909d14.js
138 ms
2227.690758d806fa29dab767.js
140 ms
2924.266d5e4ffb4dcbc93a29.js
139 ms
1802.fc511073fb105fb9daaf.js
139 ms
9772.f19b556c4e36f79191f0.js
159 ms
3197.514b751b1420ce7b3757.js
141 ms
7002.4f6dfe11b14d07f1d3b4.js
140 ms
7881.d21e57cf2550b7f0e172.js
147 ms
1848.7320b2241b7c625a8338.js
158 ms
2263.c70a0daf5405fc29fec9.js
142 ms
7190.0fb53440edcb087adde1.js
147 ms
7693.9d9b7bcd8b773b1a89b3.js
149 ms
2692.1c5ed6b340187ed301d0.js
197 ms
routes-SuperHub.c90c9e1f885060656caf.js
170 ms
1893.9c2fa305546692ae713e.js
198 ms
Header.cc0271e9369e5183260a.js
199 ms
core-icons-chevron-up-down-svg.6aae957df71e6f4c5e24.js
197 ms
6305.8c65268a950c8d658cb0.js
198 ms
element.js
53 ms
4247.2e3bc086093f74733dec.js
169 ms
2415.7607210468bf950ad0a3.js
168 ms
routes-Doc.61fd479c80915df37fd4.js
165 ms
Footer.c6ec460c7a0cc957c49a.js
164 ms
routes-PageNotFound.95febba4e34ebaaeef07.js
157 ms
518.887c7484ccb885166643.js
171 ms
Editor.cc46ca5262003557ef2c.js
172 ms
core-icons-x-circle-svg.abc0e0ea5b7f9dff667c.js
141 ms
core-icons-suggested-edits-svg.8d2d8ac2fd22ded9238d.js
140 ms
240.582ef682cbbd874acc98.js
151 ms
590.36c87d11e27a93ea4729.js
153 ms
1124.930454f2ac8ccb4c6675.js
160 ms
1468.5cb076b790e76c72c28b.js
165 ms
2518.3c0e262ad3adb9a78636.js
159 ms
8886.dcc191b028291566d2f5.js
159 ms
1068.2695744a6f89ecdd80ce.js
161 ms
c88e191-small-Leanplum_Logo_White.png
54 ms
%7B%7BimageUrl%7D%7D
381 ms
analytics.js
39 ms
fs.js
75 ms
2712.601d66d2c643c298c275.js
125 ms
routes-Reference.bbad4653ad0cab892a3b.js
127 ms
core-icons-more-vertical-svg.4822b3f831e11095980d.js
126 ms
core-icons-lock-svg.70942d3ee6bad6267696.js
137 ms
core-icons-arrow-up-right-svg.8ec73f7e322d79a2695b.js
130 ms
core-icons-arrow-right-svg.eadb74658f93b4e7d75f.js
155 ms
routes-Changelog.f92c18a7575b149de3c9.js
142 ms
2637.30396cb0ceab7931cd53.js
140 ms
4674.31218b9d4e9d241ceed1.js
138 ms
List.62412c898b63384370ad.js
140 ms
rmdx.ded238ac8f266d43b0bf.js
182 ms
5379.1a32070cb9d4aa3cd6a2.js
161 ms
routes-Landing.ad83c772119d83098835.js
135 ms
routes-Discuss.20c88dfc2758dedb26b7.js
133 ms
core-icons-star-svg.b834e1612cb2af1e174e.js
103 ms
core-icons-trending-up-svg.0dd920b0698e57f75afa.js
113 ms
core-icons-callout-info-svg.79b14e8568c9cecbc827.js
116 ms
5149.b66bdcdf59159e02f1bf.js
122 ms
CustomPage.a98f4145d85c39f2f951.js
119 ms
Post.22025fdb3911a0bac567.js
137 ms
core-icons-webhook-svg.fe540ea1c09e1c0e0247.js
127 ms
13d8dde474942669736ac81985cd072d.ttf
149 ms
docs.leanplum.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
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
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
Missing source maps for large first-party JavaScript
docs.leanplum.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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: