2.8 sec in total
149 ms
2.1 sec
490 ms
Welcome to i.john.do homepage info - get ready to check I John best content for Pakistan right away, or after learning these important things about i.john.do
CloudApp screen recorder software for Mac & PC. Record video, webcam, GIFs, capture your screen and share it instantly to the cloud, all in one easy-to-use app.
Visit i.john.doWe analyzed I.john.do page load time and found that the first response time was 149 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
i.john.do performance score
149 ms
182 ms
16 ms
43 ms
45 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original I.john.do, 12% (10 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (414 ms) relates to the external source Js.recurly.com.
Page size can be reduced by 279.5 kB (18%)
1.5 MB
1.3 MB
In fact, the total size of I.john.do main page is 1.5 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 24.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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.4 kB or 74% of the original size.
Potential reduce by 39.8 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. I John images are well optimized though.
Potential reduce by 213.3 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 213.3 kB or 54% of the original size.
Potential reduce by 2.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. I.john.do needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 79% of the original size.
Number of requests can be reduced by 30 (42%)
72
42
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I John. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.getcloudapp.com
149 ms
analytics.min.js
182 ms
normalize.css
16 ms
magnific.css
43 ms
referrals.css
45 ms
help.css
46 ms
bootstrap.css
47 ms
ouibounce.css
52 ms
application.css
66 ms
css
97 ms
js.cookie.js
49 ms
jquery.min.js
84 ms
chosen.jquery.min.js
84 ms
waitforimages.min.js
47 ms
waypoints.min.js
56 ms
moment.min.js
55 ms
magnific.min.js
78 ms
application.js
59 ms
teams.js
57 ms
jssor.sliders.mini.js
80 ms
ouibounce.min.js
78 ms
recurly.js
414 ms
2570540166.js
78 ms
widgets.js
50 ms
amplitude-2.9.0-min.gz.js
57 ms
track.js
48 ms
mixpanel-2-latest.min.js
170 ms
w.js
125 ms
77 ms
analytics.js
97 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
183 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
220 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
250 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
250 ms
EInbV5DfGHOiMmvb1Xr-hpS3E-kSBmtLoNJPDtbj2Pk.ttf
251 ms
logo_cloudapp_black.png
15 ms
bgphoto.jpg
57 ms
ico_google_plus.png
50 ms
logos_os.png
53 ms
logos.png
50 ms
img_step1_files.png
53 ms
app_image@2x.jpg
53 ms
avatar4.png
52 ms
avatar3.png
52 ms
avatar2.png
53 ms
avatar1.png
55 ms
carousel-arrows.png
54 ms
ico_take_screenshot.png
54 ms
take_screenshot.jpg
161 ms
take_screenshot_annotate.jpg
162 ms
share_link_slack.jpg
161 ms
ico_record_screen.png
158 ms
record_screen.jpg
162 ms
record_screen_settings.jpg
163 ms
share_link_skype.jpg
162 ms
ico_record_selfie.png
163 ms
record_selfie.jpg
165 ms
share_link_email.jpg
164 ms
ico_pro_unlimited.png
166 ms
ico_pro_password.png
165 ms
ico_pro_customize.png
165 ms
ico_pro_autodestroy.png
165 ms
ico_pro_domain.png
166 ms
ico_pro_annotations.png
166 ms
xjAJXh38I15wypJXxuGMBiwlidHJgAgmTjOEEzwu1L8.ttf
183 ms
PRmiXeptR36kaC0GEAetxt6Naowg1QhaIq8kLGtQSos.ttf
181 ms
PRmiXeptR36kaC0GEAetxs1QGe9x6ME_FQCWJB3n6z8.ttf
180 ms
PRmiXeptR36kaC0GEAetxjdGNerWpg2Hn6A-BxWgZ_I.ttf
192 ms
PRmiXeptR36kaC0GEAetxkdJXfhP-2RmnAuS9A2rxpE.ttf
193 ms
loader0.js
220 ms
sign-up-modal.png
59 ms
ico_card.png
54 ms
ico_privacy.png
60 ms
ico_callendar.png
54 ms
tick.png
52 ms
ico_risk_free.png
53 ms
ico_ssl.png
59 ms
collect
47 ms
collect
72 ms
3741-141-10-9243.js
31 ms
chartbeat.js
96 ms
page.gif
35 ms
application2.js
112 ms
ping
18 ms
i.john.do SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I.john.do can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that I.john.do 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.
i.john.do
Open Graph data is detected on the main page of I John. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: