4.3 sec in total
17 ms
3.1 sec
1.1 sec
Welcome to prettygee.wordpress.com homepage info - get ready to check Pretty Gee Wordpress best content for United States right away, or after learning these important things about prettygee.wordpress.com
Live. Laugh. Love.
Visit prettygee.wordpress.comWe analyzed Prettygee.wordpress.com page load time and found that the first response time was 17 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
prettygee.wordpress.com performance score
17 ms
490 ms
118 ms
127 ms
145 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Prettygee.wordpress.com, 16% (21 requests) were made to Pixel.wp.com and 14% (18 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Prettygee.files.wordpress.com.
Page size can be reduced by 555.8 kB (17%)
3.3 MB
2.8 MB
In fact, the total size of Prettygee.wordpress.com main page is 3.3 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 2.5 MB which makes up the majority of the site volume.
Potential reduce by 72.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 72.0 kB or 78% of the original size.
Potential reduce by 7.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. Pretty Gee Wordpress images are well optimized though.
Potential reduce by 450.4 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 450.4 kB or 70% of the original size.
Potential reduce by 25.6 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. Prettygee.wordpress.com needs all CSS files to be minified and compressed as it can save up to 25.6 kB or 47% of the original size.
Number of requests can be reduced by 74 (61%)
121
47
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pretty Gee Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
prettygee.wordpress.com
17 ms
prettygee.wordpress.com
490 ms
118 ms
127 ms
145 ms
style.css
139 ms
gprofiles.js
331 ms
wpgroho.js
138 ms
141 ms
style.css
137 ms
135 ms
725X1342.skimlinks.js
241 ms
w.js
136 ms
merriweather.css
35 ms
tarp-copy_21.jpg
526 ms
2014-emailteaser.png
130 ms
11910446_773648789427534_51031695_n.jpg
446 ms
sdk.js
596 ms
rss.png
444 ms
334 ms
track_39972.gif
331 ms
widgets.js
369 ms
loading.gif
54 ms
bg-nav.png
54 ms
nav-div.png
137 ms
nav-active.png
137 ms
media-icons.png
234 ms
post-separator.gif
138 ms
info-bar.png
138 ms
icons.png
232 ms
blockquote.png
254 ms
search.png
247 ms
widget-title-purple-large.png
317 ms
bg-lightgray.png
316 ms
cropped-dsc02429.jpg
338 ms
whimsical-romantic.png
2245 ms
img_0521-0.jpg
640 ms
11325687_1484850251841563_1307119323_n.jpg
608 ms
11296862_422133947994241_168820066_n.jpg
655 ms
11419260_651530561613064_1532185871_n.jpg
666 ms
10554214_960226430668009_853189275_n.jpg
654 ms
10666259_1519331651665209_1828480331_n.jpg
704 ms
Genericons.svg
180 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
2 ms
master.html
347 ms
Noticons.svg
187 ms
BaABdRAi2AAAA
88 ms
merriweather-bold-webfont.ttf
178 ms
merriweather-regular-webfont.ttf
253 ms
merriweather-light-webfont.ttf
252 ms
px.gif
399 ms
342 ms
hovercard.css
273 ms
services.css
331 ms
share
377 ms
g.gif
316 ms
count.json
407 ms
graph.facebook.com
540 ms
share
465 ms
count.json
406 ms
graph.facebook.com
651 ms
share
462 ms
count.json
404 ms
graph.facebook.com
678 ms
share
481 ms
count.json
400 ms
graph.facebook.com
689 ms
share
461 ms
count.json
399 ms
graph.facebook.com
723 ms
share
475 ms
count.json
456 ms
graph.facebook.com
687 ms
268 ms
px.gif
320 ms
g.gif
265 ms
g.gif
257 ms
g.gif
258 ms
g.gif
257 ms
g.gif
257 ms
g.gif
348 ms
g.gif
347 ms
g.gif
348 ms
g.gif
347 ms
g.gif
347 ms
g.gif
350 ms
g.gif
351 ms
g.gif
350 ms
g.gif
350 ms
g.gif
350 ms
g.gif
350 ms
g.gif
377 ms
g.gif
393 ms
g.gif
393 ms
g.gif
392 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
80 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
154 ms
global-print.css
74 ms
jquery.js
64 ms
syndication
148 ms
512132744344649728
166 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
63 ms
postmessage.js
59 ms
jed.js
58 ms
underscore.min.js
59 ms
info.json
142 ms
85 ms
xd_arbiter.php
309 ms
link
87 ms
track.php
123 ms
jquery.wpcom-proxy-request.js
29 ms
44 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
7 ms
likes-rest.js
4 ms
NMKBzChh_normal.jpg
80 ms
32 ms
batch
100 ms
jot.html
2 ms
3 ms
04f09e244e72684424f101bd2c9570ad
48 ms
866b1cf424dba302ad72171ba5b7890c
137 ms
764d7d06e90151d027e78a0750dc3bff
119 ms
noticons.css
7 ms
style.css
6 ms
cd73d495eb60ef748de5f713070d0339
44 ms
030fd1a21a4cba5c7b76bbd82580460c
72 ms
Noticons.svg
18 ms
prettygee.wordpress.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prettygee.wordpress.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 Prettygee.wordpress.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.
prettygee.wordpress.com
Open Graph data is detected on the main page of Pretty Gee Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: