10 sec in total
730 ms
3.2 sec
6 sec
Click here to check amazing Commentarypress content. Otherwise, check out these important facts you probably never knew about commentarypress.com
Visit commentarypress.comWe analyzed Commentarypress.com page load time and found that the first response time was 730 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
commentarypress.com performance score
730 ms
169 ms
24 ms
205 ms
6 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 9% of them (11 requests) were addressed to the original Commentarypress.com, 47% (60 requests) were made to 0.gravatar.com and 41% (52 requests) were made to 1.gravatar.com. The less responsive or slowest element that took the longest time to load (917 ms) belongs to the original domain Commentarypress.com.
Page size can be reduced by 684.5 kB (23%)
2.9 MB
2.3 MB
In fact, the total size of Commentarypress.com main page is 2.9 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. 35% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 199.1 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 29.5 kB, which is 12% 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 199.1 kB or 82% of the original size.
Potential reduce by 460.9 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. Obviously, Commentarypress needs image optimization as it can save up to 460.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 460 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 24.0 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. Commentarypress.com needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 82% of the original size.
Number of requests can be reduced by 10 (8%)
126
116
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Commentarypress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
www.commentarypress.com
730 ms
style.css
169 ms
css
24 ms
comment-reply.min.js
205 ms
devicepx-jetpack.js
6 ms
ga.js
161 ms
ad516503a11cd5ca435acc9bb6523536
123 ms
a9c519f9350641822ae157ac3f4ffbdb
137 ms
4069ecab2eb12c2fa5bb01b216fa3c9f
195 ms
ad516503a11cd5ca435acc9bb6523536
195 ms
a4edaf89b0fcbe074be1d29f98a207bc
206 ms
83e372e3eafa59468bbbe0806d3ebb7b
209 ms
83e372e3eafa59468bbbe0806d3ebb7b
208 ms
4cf28ac651e04bde3c670afdc2e60675
239 ms
5d4e7b1da671f91036a8d960be54fce8
123 ms
158d107091993bb2a7fd846fefb162b9
147 ms
7b2ebfa904d1c2ca08e64df6bb00499c
193 ms
756dfe4db193b852a2de04324c051cb9
209 ms
body-bg.png
132 ms
cropped-banner_anegada_british_virgin_islands_1960.png
917 ms
timeline_1_cynthia_and_ray_franz.png
487 ms
timeline_3_franz_wedding_2_28_1959.png
374 ms
timeline_4_missionary_work_dominican_republic_large.png
586 ms
timeline_6_passport_1964.png
314 ms
timeline_7_muchacho_late_1990s_and-50th_wedding_anniversary_large.png
481 ms
timeline_9_cynthia_franz_november_2013-172x300.jpg
405 ms
ad516503a11cd5ca435acc9bb6523536
128 ms
ad516503a11cd5ca435acc9bb6523536
129 ms
ad516503a11cd5ca435acc9bb6523536
129 ms
ad516503a11cd5ca435acc9bb6523536
127 ms
ad516503a11cd5ca435acc9bb6523536
127 ms
ad516503a11cd5ca435acc9bb6523536
127 ms
ad516503a11cd5ca435acc9bb6523536
127 ms
ad516503a11cd5ca435acc9bb6523536
126 ms
ad516503a11cd5ca435acc9bb6523536
124 ms
ad516503a11cd5ca435acc9bb6523536
124 ms
ad516503a11cd5ca435acc9bb6523536
124 ms
ad516503a11cd5ca435acc9bb6523536
123 ms
ad516503a11cd5ca435acc9bb6523536
124 ms
ad516503a11cd5ca435acc9bb6523536
122 ms
ad516503a11cd5ca435acc9bb6523536
121 ms
ad516503a11cd5ca435acc9bb6523536
158 ms
ad516503a11cd5ca435acc9bb6523536
157 ms
ad516503a11cd5ca435acc9bb6523536
158 ms
ad516503a11cd5ca435acc9bb6523536
156 ms
ad516503a11cd5ca435acc9bb6523536
156 ms
ad516503a11cd5ca435acc9bb6523536
156 ms
ad516503a11cd5ca435acc9bb6523536
155 ms
ad516503a11cd5ca435acc9bb6523536
158 ms
ad516503a11cd5ca435acc9bb6523536
153 ms
ad516503a11cd5ca435acc9bb6523536
152 ms
ad516503a11cd5ca435acc9bb6523536
152 ms
ad516503a11cd5ca435acc9bb6523536
152 ms
ad516503a11cd5ca435acc9bb6523536
153 ms
ad516503a11cd5ca435acc9bb6523536
150 ms
ad516503a11cd5ca435acc9bb6523536
153 ms
RJMlAoFXXQEzZoMSUteGWCZ2oysoEQEeKwjgmXLRnTc.ttf
55 ms
__utm.gif
64 ms
ad516503a11cd5ca435acc9bb6523536
119 ms
ad516503a11cd5ca435acc9bb6523536
119 ms
ad516503a11cd5ca435acc9bb6523536
118 ms
ad516503a11cd5ca435acc9bb6523536
120 ms
ad516503a11cd5ca435acc9bb6523536
115 ms
ad516503a11cd5ca435acc9bb6523536
113 ms
ad516503a11cd5ca435acc9bb6523536
113 ms
ad516503a11cd5ca435acc9bb6523536
112 ms
ad516503a11cd5ca435acc9bb6523536
113 ms
ad516503a11cd5ca435acc9bb6523536
112 ms
ad516503a11cd5ca435acc9bb6523536
110 ms
ad516503a11cd5ca435acc9bb6523536
110 ms
ad516503a11cd5ca435acc9bb6523536
110 ms
ad516503a11cd5ca435acc9bb6523536
108 ms
ad516503a11cd5ca435acc9bb6523536
111 ms
ad516503a11cd5ca435acc9bb6523536
115 ms
ad516503a11cd5ca435acc9bb6523536
120 ms
ad516503a11cd5ca435acc9bb6523536
125 ms
ad516503a11cd5ca435acc9bb6523536
123 ms
ad516503a11cd5ca435acc9bb6523536
124 ms
ad516503a11cd5ca435acc9bb6523536
124 ms
ad516503a11cd5ca435acc9bb6523536
125 ms
ad516503a11cd5ca435acc9bb6523536
121 ms
ad516503a11cd5ca435acc9bb6523536
119 ms
ad516503a11cd5ca435acc9bb6523536
106 ms
ad516503a11cd5ca435acc9bb6523536
115 ms
ad516503a11cd5ca435acc9bb6523536
117 ms
ad516503a11cd5ca435acc9bb6523536
125 ms
ad516503a11cd5ca435acc9bb6523536
125 ms
ad516503a11cd5ca435acc9bb6523536
128 ms
512f4eee0efdbdd7d1f93cbeefa98cda
143 ms
ad516503a11cd5ca435acc9bb6523536
140 ms
ad516503a11cd5ca435acc9bb6523536
146 ms
311325e97601351c02dc03d34838b698
119 ms
ad516503a11cd5ca435acc9bb6523536
121 ms
ad516503a11cd5ca435acc9bb6523536
139 ms
ad516503a11cd5ca435acc9bb6523536
138 ms
ad516503a11cd5ca435acc9bb6523536
134 ms
ad516503a11cd5ca435acc9bb6523536
139 ms
ad516503a11cd5ca435acc9bb6523536
138 ms
ad516503a11cd5ca435acc9bb6523536
121 ms
ad516503a11cd5ca435acc9bb6523536
134 ms
ad516503a11cd5ca435acc9bb6523536
103 ms
ad516503a11cd5ca435acc9bb6523536
110 ms
ad516503a11cd5ca435acc9bb6523536
105 ms
ad516503a11cd5ca435acc9bb6523536
104 ms
ad516503a11cd5ca435acc9bb6523536
107 ms
ad516503a11cd5ca435acc9bb6523536
108 ms
ad516503a11cd5ca435acc9bb6523536
76 ms
ad516503a11cd5ca435acc9bb6523536
116 ms
ad516503a11cd5ca435acc9bb6523536
111 ms
ad516503a11cd5ca435acc9bb6523536
76 ms
ad516503a11cd5ca435acc9bb6523536
71 ms
ad516503a11cd5ca435acc9bb6523536
74 ms
ad516503a11cd5ca435acc9bb6523536
101 ms
ad516503a11cd5ca435acc9bb6523536
73 ms
ad516503a11cd5ca435acc9bb6523536
101 ms
ad516503a11cd5ca435acc9bb6523536
106 ms
ad516503a11cd5ca435acc9bb6523536
105 ms
ad516503a11cd5ca435acc9bb6523536
110 ms
ad516503a11cd5ca435acc9bb6523536
65 ms
ad516503a11cd5ca435acc9bb6523536
59 ms
ad516503a11cd5ca435acc9bb6523536
99 ms
ad516503a11cd5ca435acc9bb6523536
58 ms
ad516503a11cd5ca435acc9bb6523536
97 ms
ad516503a11cd5ca435acc9bb6523536
101 ms
ad516503a11cd5ca435acc9bb6523536
54 ms
ad516503a11cd5ca435acc9bb6523536
69 ms
ad516503a11cd5ca435acc9bb6523536
99 ms
ad516503a11cd5ca435acc9bb6523536
96 ms
commentarypress.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Commentarypress.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 Commentarypress.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.
commentarypress.com
Open Graph description is not detected on the main page of Commentarypress. 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: