4.4 sec in total
61 ms
3.8 sec
521 ms
Click here to check amazing What I Live For content. Otherwise, check out these important facts you probably never knew about whatilivefor.net
Visit whatilivefor.netWe analyzed Whatilivefor.net page load time and found that the first response time was 61 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whatilivefor.net performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value3.9 s
53/100
25%
Value4.0 s
81/100
10%
Value2,230 ms
6/100
30%
Value0.124
83/100
15%
Value9.8 s
28/100
10%
61 ms
130 ms
70 ms
122 ms
86 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Whatilivefor.net, 17% (24 requests) were made to Apis.google.com and 15% (22 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Business2blogger.com.
Page size can be reduced by 303.5 kB (19%)
1.6 MB
1.3 MB
In fact, the total size of Whatilivefor.net main page is 1.6 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.1 MB which makes up the majority of the site volume.
Potential reduce by 102.5 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 102.5 kB or 82% of the original size.
Potential reduce by 21.2 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. What I Live For images are well optimized though.
Potential reduce by 114.1 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 114.1 kB or 49% of the original size.
Potential reduce by 65.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. Whatilivefor.net needs all CSS files to be minified and compressed as it can save up to 65.6 kB or 74% of the original size.
Number of requests can be reduced by 82 (60%)
137
55
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What I Live For. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
whatilivefor.net
61 ms
www.whatilivefor.net
130 ms
3375562265-css_bundle_v2.css
70 ms
authorization.css
122 ms
plusone.js
86 ms
show_ads.js
53 ms
widget.js
70 ms
load.min.js
68 ms
qvY94o1z5uj6ugwoo3L19oLKNi8gan1Z.js
40 ms
3226477086-widgets.js
63 ms
analytics.js
69 ms
gtm.js
72 ms
cb=gapi.loaded_0
53 ms
cb=gapi.loaded_1
53 ms
google_top_exp.js
52 ms
Blog%2Bheader%2B1.jpg
125 ms
icon18_wrench_allbkg.png
50 ms
ca-pub-2988430611959394.js
111 ms
zrt_lookup.html
181 ms
show_ads_impl.js
109 ms
icon18_edit_allbkg.gif
98 ms
IMG_4150.JPG
202 ms
IMG_3305.JPG
172 ms
2015-06-13.jpg
92 ms
paging_dot.png
88 ms
get_custom_js
164 ms
pixel.png
82 ms
photo.jpg
161 ms
gprofile_button-16.png
89 ms
friendconnect.js
151 ms
whatilivefor-2.jpg
188 ms
CraftingandCreativitybutton125x125.jpg
189 ms
mmbcommunitybutton.png
186 ms
icon18_email.gif
80 ms
share_buttons_20_3.png
82 ms
DSC_0733.JPG
156 ms
collect
91 ms
blank.html
30 ms
navbar.g
93 ms
collect
82 ms
ads
304 ms
osd.js
33 ms
ads
283 ms
icons_peach.png
62 ms
platform:gapi.iframes.style.common.js
58 ms
arrows-light.png
52 ms
5919474882_d0337b95c7_o.png
120 ms
show_widget
79 ms
show_widget
79 ms
tc.js
38 ms
vglnk.js
76 ms
albuquerque-new-mexico-808x480-CU031224-002.jpg
681 ms
ads
475 ms
cb=gapi.loaded_0
119 ms
cb=gapi.loaded_1
153 ms
fastbutton
219 ms
p
181 ms
dark.png
143 ms
pixel.gif
198 ms
87690383.jpg
198 ms
362565459.jpg
195 ms
251876505.jpg
196 ms
pixel.gif
186 ms
390166637.jpg
186 ms
413050355.jpg
185 ms
415279687.jpg
185 ms
cb=gapi.loaded_2
129 ms
cb=gapi.loaded_3
159 ms
fastbutton
160 ms
fastbutton
211 ms
fastbutton
207 ms
fastbutton
216 ms
fastbutton
213 ms
follow
210 ms
148 ms
ifr
77 ms
m_js_controller.js
97 ms
abg.js
141 ms
postmessageRelay
283 ms
cb=gapi.loaded_4
61 ms
cb=gapi.loaded_0
115 ms
cb=gapi.loaded_1
124 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
116 ms
google.blog.js
282 ms
gadgets-ltr.css
279 ms
postmessageRelay
270 ms
grlryt2bdKIyfMSOhzd1eA.woff
385 ms
v2
254 ms
mapuid
253 ms
favicon
391 ms
googlelogo_color_112x36dp.png
379 ms
nessie_icon_tiamat_white.png
194 ms
rs=AGLTcCPaIpnvYdvK9nEPlKCC4baoCWq5dw
176 ms
rs=AGLTcCP1XWuWX_iCC9WgWr0vKsRUFWxeag
183 ms
rs=AGLTcCNLi0WuU6mSKfpy45PgbYdTWlDqhQ
226 ms
s
273 ms
x_button_blue2.png
179 ms
8273589528301717089
204 ms
3193398744-postmessagerelay.js
417 ms
rpc:shindig_random.js
218 ms
demconf.jpg
155 ms
trash.gif
123 ms
plus.gif
165 ms
smallEnvelope.jpg
163 ms
fc-edit.png
162 ms
do-not-enter.gif
167 ms
unblock.gif
167 ms
d-QWLnp4didxos_6urzFtg.woff
97 ms
vxNK-E6B13CyehuDCmvQvw.woff
290 ms
dpx
95 ms
ping
101 ms
mod_gadget_common__en_US.js
238 ms
mod_gadget_members__en_US.js
97 ms
263 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
39 ms
ca.png
300 ms
xrefid.xgi
29 ms
domains
62 ms
cb=gapi.loaded_0
14 ms
52154.gif
34 ms
52154.gif
33 ms
rpc
98 ms
rpc
175 ms
rpc
88 ms
rpc
89 ms
47154.gif
8 ms
dimage
88 ms
heart%25252Bsunglasses%25252Blove%25252Bone%25252Banother%25252Bflickr.JPG
96 ms
melissa%2Band%2Bi.jpg
122 ms
QFlmO2PTdJ6wJzGSWwec7KPXhqwLL_MF2n_-4tSUr_7DPp14wvsXWOTb6vd9NGtzgLZ8kAAlslt_v-4I2MO108yxyowZiAGxW2dvgNNmn_inVaKFAB3-N03jdGtwKQEMPJ_SufHKUwyov3a528PZZ3Q94_HpKOOTAefNnmuzX5o0a6lPbvsfEjm8URexmYxIWt-UJHuXDYoI4N-sctJUNSJsSLGvs-BU7WQPKptngovGpi4uEm_M7rgAOqkgP_rPLal4wa0A3Ck
63 ms
E8csuToU8zRRKVRyv4KjnKPXhqwLL_MF2n_-4tSUr_7DPp14wvsXWOTb6vd9NGtzgLZ8kAAlslt_v-4I2MO10zeVj68hyN_l9f9XToLIRW413siBQpPR7PfVXTeTI4ciAcSCKZvBNAv8_B6eTdnCW7cqcmE_YZJdRS_DJYOjD1gf19cQhwK0RJHy3rLk_9qblOXkXTVduLU6Mw4nKXhy-xhk5QB37L4QdRVThkbYWM5t4U5amtlFAGyZeKXKpv9uHZmbv1F8JkY
63 ms
ovef--OMGfJRKVRyv4KjnKPXhqwLL_MF2n_-4tSUr_7DPp14wvsXWOTb6vd9NGtzgLZ8kAAlslt_v-4I2MO1085f5SYYzTTykQNbxxMepQD8-v4226w4w_fVXTeTI4ciA0yU89XimX6oy7I61AZn1wfr0s_UmRluZvkCilCnhfsj2Ct478mPjV8HXyNVveMmsXdJWpBDJxTN9N3D1cXfq-1dxUpO83nSX2HVjoZ55rstd3UlPKzGO2yZeKXKpv9uHZmbv1F8JkY
62 ms
fcgaZeOZ8UewJzGSWwec7KPXhqwLL_MF2n_-4tSUr_7DPp14wvsXWOTb6vd9NGtzgLZ8kAAlslt_v-4I2MO10yI4D367ZJOoVG39s-vGJUWanRO43empME3jdGtwKQEMWZDJuCLR3-BfQaXokoswMlONviDgYWjdJ9HtU3_mkW2F3NLaccz6htFgnlSRvkBH3PQasROHfS6ZeWADmR8ZG_XLFZJAsVD6eiZomezOOSbzYCcUGOpHdply1E1gtF4ELal4wa0A3Ck
62 ms
oWbVAYw1mRBRKVRyv4KjnKPXhqwLL_MF2n_-4tSUr_7DPp14wvsXWOTb6vd9NGtzgLZ8kAAlslt_v-4I2MO108uObG1AdoKVwViLZoDvIgyiRf2IZIG55vfVXTeTI4ciFBqv1ZgOcIGA9JyNH_LHL_J_dEe-FQCF8aaGvNO4caW72w_OgAcE89EiLY9a2cszftHn8PuCD94rPtdTD93JqjdjFhBYKOQMYjkYMGAqFZFPA4jRXfyMyGyZeKXKpv9uHZmbv1F8JkY
61 ms
Ff9cCLyImtnoQbYwVNaab-J8Yhx76Vo4aRf-ynqQU8g8frdte16ayEXOItczBitYbo6Rx_qZFcrcnfR8EQYVENSSvhQbcxksoSkOQO_y3hg
61 ms
dimage
62 ms
dimage
61 ms
gfc_button_v2.gif
59 ms
b2bbutton111.png
2024 ms
activeview
16 ms
activeview
20 ms
306752634-lightbox_bundle.css
4 ms
ui
16 ms
297602417-lbx.js
14 ms
whatilivefor.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
whatilivefor.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
whatilivefor.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatilivefor.net 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 Whatilivefor.net 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.
whatilivefor.net
Open Graph description is not detected on the main page of What I Live For. 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: