7.3 sec in total
1.2 sec
5.3 sec
707 ms
Visit lovepomegranatehouse.com now to see the best up-to-date Lovepomegranatehouse content for United States and also check out these interesting facts you probably never knew about lovepomegranatehouse.com
Visit lovepomegranatehouse.comWe analyzed Lovepomegranatehouse.com page load time and found that the first response time was 1.2 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lovepomegranatehouse.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
1244 ms
30 ms
53 ms
64 ms
61 ms
Our browser made a total of 234 requests to load all elements on the main page. We found that 7% of them (17 requests) were addressed to the original Lovepomegranatehouse.com, 11% (25 requests) were made to S3.amazonaws.com and 6% (15 requests) were made to Pixel.rubiconproject.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lovepomegranatehouse.com.
Page size can be reduced by 880.9 kB (36%)
2.4 MB
1.6 MB
In fact, the total size of Lovepomegranatehouse.com main page is 2.4 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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 92.2 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.2 kB or 77% of the original size.
Potential reduce by 79.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. Lovepomegranatehouse images are well optimized though.
Potential reduce by 689.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 689.0 kB or 66% of the original size.
Potential reduce by 19.9 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. Lovepomegranatehouse.com needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 79% of the original size.
Number of requests can be reduced by 136 (64%)
213
77
The browser has sent 213 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lovepomegranatehouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.lovepomegranatehouse.com
1244 ms
css
30 ms
lph.css
53 ms
catablog.css
64 ms
commentluv.css
61 ms
jquery.js
151 ms
jquery-migrate.min.js
65 ms
commentluv.js
83 ms
jquery.min.js
29 ms
lph.js
85 ms
300a.js
47 ms
519e060926e41e1313913bc2ba8e2f4dfc3bbf14.js
32 ms
show_ads.js
7 ms
e00656d7b75683fa2fb59e02fd1473ecc5f3c605.js
23 ms
3b8c5e5213fb77ed6345cea2ed3e49a0566d4f3a.js
21 ms
pinit.js
7 ms
ga.js
26 ms
header.png
391 ms
blogherads.js
103 ms
plusone.js
396 ms
widget.gif
379 ms
ca-pub-4808271556644442.js
291 ms
zrt_lookup.html
314 ms
show_ads_impl.js
170 ms
overlay-300x250.png
226 ms
pinit_fg_en_rect_white_28.png
126 ms
ga.js
211 ms
menu-banner.png
446 ms
menu-home.png
455 ms
menu-about.png
399 ms
menu-projects.png
399 ms
menu-recipes.png
487 ms
menu-featured.png
489 ms
menu-parties.png
618 ms
menu-contact.png
585 ms
menu-advertise.png
618 ms
social-facebook.png
618 ms
social-pinterest.png
760 ms
social-twitter.png
731 ms
social-rss.png
760 ms
social-google.png
786 ms
social-instagram.png
841 ms
tab-welcome.png
1028 ms
button-read-more.png
841 ms
button-contact.png
941 ms
LPH-Button.png
246 ms
header-follow.png
908 ms
button-submit.png
924 ms
header-sponsors.png
997 ms
comment-bubble.png
995 ms
button-continue-reading.png
251 ms
Miracles.jpg
357 ms
icon_wink.gif
101 ms
miscarriage.jpg
302 ms
Screen-Shot-2015-02-26-at-1.35.52-PM.png
438 ms
DSC_0007-JPG.jpg
316 ms
TITLE.jpg
300 ms
DSC_0037-JPG.jpg
243 ms
closeit.png
315 ms
10420
156 ms
10419
214 ms
10418
243 ms
pinit_main.js
144 ms
BfQP1MR3mJNaumtWa4Tizg.ttf
214 ms
zR-6QGMCFX5j-6nbH_HpIQ.ttf
247 ms
AQQ1r0_czneVCtTD9ckSEA.ttf
297 ms
Q5N_zd0042xOVES9NXt9QqCWcynf_cDxXwCLxiixG1c.ttf
313 ms
gpt.js
203 ms
12450357491321
270 ms
init
200 ms
bid
248 ms
pql
197 ms
headertag
322 ms
fastlane.json
381 ms
likebox.php
296 ms
piwik.js
149 ms
beacon.js
192 ms
quant.js
189 ms
nodetag.js
676 ms
nodetag.js
675 ms
sheknows-affiliate_tag.js
236 ms
px.js
220 ms
ads
295 ms
286 ms
count.json
284 ms
osd.js
109 ms
__utm.gif
65 ms
ads
291 ms
ads
306 ms
piwik.php
253 ms
pubads_impl_81.js
95 ms
pixel;r=1656870518;a=p-332Zai8Qjq55s;labels=bh.lovepomegranatehouse947844.diy.home;fpan=1;fpa=P0-1239327369-1456806845804;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456806845803;tzo=-180;ref=;url=http%3A%2F%2Fwww.lovepomegranatehouse.com%2F;ogl=locale.en_US%2Ctype.website%2Ctitle.Love%252C%20Pomegranate%20House%20-%2Curl.http%3A%2F%2Fwww%252Elovepomegranatehouse%252Ecom%2Csite_name.Love%252C%20Pomegranate%20House
75 ms
pixel
136 ms
cb=gapi.loaded_0
61 ms
cb=gapi.loaded_1
116 ms
badge
163 ms
search.js
51 ms
Large_Rotating_Ad_-_300x250.html
30 ms
cc.js
140 ms
container.html
39 ms
FbUd6dZS1Af.css
369 ms
dGJLq38YL-C.css
394 ms
_rx8naC75Dy.js
502 ms
x5F9OMjKyLw.js
583 ms
ICDbTSzjQEg.js
500 ms
TTCre3391I0.js
498 ms
pyp-logo-vert-large-300-250.png
68 ms
search.js
65 ms
pixel
60 ms
fastlane.json
245 ms
tap.php
38 ms
usersync
36 ms
1
49 ms
postmessageRelay
72 ms
pixel
38 ms
1147864435406181620
125 ms
abg.js
234 ms
m_js_controller.js
246 ms
googlelogo_color_112x36dp.png
232 ms
ca.png
446 ms
rs=AGLTcCPuAgO4ibCoNY7Z7uvsgRNS_6x51Q
22 ms
rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA
39 ms
rs=AGLTcCNDCD2FX1GmFI4h9QOi1JonWtDyWA
115 ms
174 ms
ca.png
418 ms
photo.jpg
234 ms
api.js
154 ms
core:rpc:shindig.random:shindig.sha1.js
246 ms
2536007149-postmessagerelay.js
224 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
234 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
263 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
303 ms
rs=AGLTcCNDCD2FX1GmFI4h9QOi1JonWtDyWA
84 ms
bhastyles.css
61 ms
ads
157 ms
BHPN_comScore_HomeDIY_160x23.jpg
59 ms
s
48 ms
x_button_blue2.png
34 ms
rs=AGLTcCNDCD2FX1GmFI4h9QOi1JonWtDyWA
44 ms
rand=1990356352
13 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
11 ms
10278.js
48 ms
moatad.js
173 ms
aa.js
46 ms
sync
59 ms
941834_375269125939576_1004296097_n.png
296 ms
1375186_375268869272935_26677799_n.png
335 ms
11781684_1643363135910228_2093471235672389836_n.jpg
389 ms
11224533_945522072137419_3109983885833363298_n.jpg
418 ms
1379841_10150004552801901_469209496895221757_n.jpg
407 ms
12391033_866582040129358_2039925258742076664_n.jpg
418 ms
12144782_1000054970025035_8303570654274211147_n.jpg
426 ms
wL6VQj7Ab77.png
53 ms
s7jcwEQH7Sx.png
54 ms
217322-15.js
155 ms
ads
33 ms
container.html
8 ms
jstag
21 ms
aa.js
5 ms
osd.js
4 ms
1
19 ms
sync
10 ms
i.js
106 ms
acj
147 ms
js
38 ms
pd
71 ms
ads
41 ms
rr
10 ms
ri
9 ms
I6-MnjEovm5.js
62 ms
vlXaquuXMrr.js
61 ms
js
57 ms
aa.js
23 ms
ads
273 ms
cd0db2e8-f458-d1cd-ab04-98cee0cf1598
39 ms
openx
11 ms
pixel
81 ms
openx
14 ms
p.js
51 ms
sd
40 ms
sd
58 ms
p.js
50 ms
emily.html
17 ms
emily.html
22 ms
p.js
61 ms
pixel.htm
54 ms
channels.js
27 ms
sd
37 ms
i
35 ms
sd
34 ms
tap.php
83 ms
ddc.htm
44 ms
tap.php
9 ms
sd
46 ms
rubicon.ashx
116 ms
rubicon
5 ms
tap.php
9 ms
pixel
12 ms
rubicon
10 ms
pull_sync
9 ms
tap.php
38 ms
tap.php
47 ms
tap.php
8 ms
tap.php
35 ms
tap.php
36 ms
tap.php
29 ms
tap.php
29 ms
tap.php
11 ms
548331575875155245
23 ms
tap.php
17 ms
tap.php
11 ms
tap.php
7 ms
rt=ifr
18 ms
icon1.png
38 ms
s.js
225 ms
s.js
209 ms
ui
97 ms
5907
72 ms
tpc=na_id
23 ms
pixel
21 ms
g.json
16 ms
tpid=6962319378860130040
8 ms
px
5 ms
7 ms
universalpixel.js
11 ms
receive
20 ms
362738.gif
7 ms
universalpixel.js
11 ms
universalpixel.js
10 ms
UPug
19 ms
pixel.js
11 ms
dpsync.html
12 ms
adrad.php
431 ms
adrad.php
447 ms
lovepomegranatehouse.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lovepomegranatehouse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
lovepomegranatehouse.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lovepomegranatehouse.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Lovepomegranatehouse.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.
lovepomegranatehouse.com
Open Graph description is not detected on the main page of Lovepomegranatehouse. 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: