3.4 sec in total
1 sec
2.2 sec
97 ms
Click here to check amazing Planr content. Otherwise, check out these important facts you probably never knew about planr.com
Planr is an intelligent platform revolutionizing private equity portfolio management that helps optimize investment strategies and maximize returns.
Visit planr.comWe analyzed Planr.com page load time and found that the first response time was 1 sec and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
planr.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value6.3 s
11/100
25%
Value5.6 s
52/100
10%
Value720 ms
41/100
30%
Value0.416
23/100
15%
Value5.5 s
71/100
10%
1041 ms
274 ms
276 ms
25 ms
363 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 84% of them (42 requests) were addressed to the original Planr.com, 10% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Planr.com.
Page size can be reduced by 680.1 kB (87%)
785.3 kB
105.2 kB
In fact, the total size of Planr.com main page is 785.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. CSS take 673.7 kB which makes up the majority of the site volume.
Potential reduce by 92.0 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 92.0 kB or 82% of the original size.
Potential reduce by 588.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. Planr.com needs all CSS files to be minified and compressed as it can save up to 588.1 kB or 87% of the original size.
Number of requests can be reduced by 27 (63%)
43
16
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
planr.com
1041 ms
wp-emoji-release.min.js
274 ms
layerslider.css
276 ms
css
25 ms
settings.css
363 ms
style.css
815 ms
font-awesome.css
276 ms
animations.css
454 ms
media.css
454 ms
ipad.css
365 ms
masterslider.main.css
503 ms
custom.css
451 ms
greensock.js
545 ms
jquery.js
734 ms
jquery-migrate.min.js
542 ms
layerslider.kreaturamedia.jquery.js
636 ms
layerslider.transitions.js
619 ms
jquery.themepunch.tools.min.js
882 ms
jquery.themepunch.revolution.min.js
882 ms
css
14 ms
css
25 ms
comment-reply.min.js
439 ms
modernizr-min.js
462 ms
jquery.carouFredSel-6.2.1-min.js
533 ms
jquery.cycle.js
620 ms
jquery.prettyPhoto-min.js
581 ms
jquery.flexslider-min.js
602 ms
jquery.fitvids-min.js
600 ms
main.js
886 ms
wp-embed.min.js
641 ms
r.jpg
93 ms
page_title_bg.png
191 ms
welive.jpg
203 ms
fundit1.jpg
105 ms
spark.jpg
201 ms
shrink.jpg
288 ms
robot1.jpg
213 ms
pta.jpg
444 ms
haiku.jpg
444 ms
jezabel.jpg
441 ms
kwonjaehwa.jpg
442 ms
littlestar.jpg
440 ms
w21.jpg
444 ms
w71.jpg
571 ms
8c9q46CAcsp9TiRX9KLgZMDdSZkkecOE1hvV7ZHvhyU.ttf
9 ms
G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf
9 ms
0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf
8 ms
icomoon.woff
437 ms
PIPMHY90P7jtyjpXuZ2cLCZ2oysoEQEeKwjgmXLRnTc.ttf
3 ms
lILlYDvubYemzYzN7GbLkJS3E-kSBmtLoNJPDtbj2Pk.ttf
8 ms
planr.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
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.
planr.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
planr.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 Planr.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 Planr.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.
planr.com
Open Graph description is not detected on the main page of Planr. 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: