2.8 sec in total
77 ms
2.2 sec
453 ms
Welcome to 1blog2lives.com homepage info - get ready to check 1 Blog 2 Lives best content right away, or after learning these important things about 1blog2lives.com
Visit 1blog2lives.comWe analyzed 1blog2lives.com page load time and found that the first response time was 77 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
1blog2lives.com performance score
77 ms
127 ms
43 ms
69 ms
64 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 1blog2lives.com, 54% (66 requests) were made to Scontent.cdninstagram.com and 8% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Snapwidget.com.
Page size can be reduced by 308.7 kB (16%)
2.0 MB
1.7 MB
In fact, the total size of 1blog2lives.com main page is 2.0 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. 75% 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.5 MB which makes up the majority of the site volume.
Potential reduce by 53.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 53.2 kB or 78% of the original size.
Potential reduce by 10.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. 1 Blog 2 Lives images are well optimized though.
Potential reduce by 123.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 123.3 kB or 43% of the original size.
Potential reduce by 122.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. 1blog2lives.com needs all CSS files to be minified and compressed as it can save up to 122.0 kB or 79% of the original size.
Number of requests can be reduced by 45 (39%)
116
71
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 Blog 2 Lives. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
1blog2lives.com
77 ms
www.1blog2lives.com
127 ms
webfont.js
43 ms
3375562265-css_bundle_v2.css
69 ms
gsearch.css
64 ms
authorization.css
111 ms
3226477086-widgets.js
72 ms
plusone.js
96 ms
jsapi
86 ms
css
38 ms
1B2L%2BFINAL%2B6%2B%25282%2529.jpg
79 ms
1395998_10151802272283014_802552120_n.jpg
77 ms
icon18_edit_allbkg.gif
63 ms
aaDSC_5714.jpg
72 ms
paging_dot.png
61 ms
icon18_wrench_allbkg.png
61 ms
68 ms
1263 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
36 ms
fastbutton
98 ms
fastbutton
119 ms
77 ms
share_buttons_20_3.png
18 ms
DSC_1045.JPG
69 ms
clear.gif
82 ms
fKnfV28XkldRW297cFLeqfesZW2xOQ-xsNqO47m55DA.ttf
67 ms
DK0eTGXiZjN6yA8zAEyM2S5FJMZltoAAwO2fP7iHu2o.ttf
66 ms
combined.css
62 ms
smoothDivScroll.css
57 ms
stack_161235.js
124 ms
jquery.min.js
58 ms
jquery.cycle.lite.js
66 ms
postmessageRelay
232 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
24 ms
default+en_GB.css
167 ms
default+en_GB.I.js
220 ms
cb=gapi.loaded_0
159 ms
cb=gapi.loaded_1
158 ms
analytics.js
153 ms
stackpile.api-6712054ce0.js
177 ms
12825858_463014330561289_2054743442_n.jpg
294 ms
12825815_968541013182592_1722782782_n.jpg
197 ms
10554231_1532734940361801_1568999575_n.jpg
242 ms
10401722_1549534818677309_13343029_n.jpg
258 ms
923767_1705168356434243_509775093_n.jpg
271 ms
12822501_440357872839945_998664113_n.jpg
276 ms
12825700_1537443343218402_52564331_n.jpg
249 ms
1390263_974883395939265_1656419294_n.jpg
250 ms
10611039_488884224646339_1903834819_n.jpg
302 ms
12825835_1748725562014299_879611047_n.jpg
293 ms
10013356_1086765054718867_2095025391_n.jpg
267 ms
1690012_1586241475033206_1128342412_n.jpg
289 ms
12825938_1579459332381825_446782509_n.jpg
394 ms
12383525_525443854292404_2037995272_n.jpg
352 ms
1389849_1053852784678713_1559287005_n.jpg
371 ms
914621_1196001633758290_531768516_n.jpg
351 ms
10843933_874082112718246_831412315_n.jpg
335 ms
12822285_1579380935715667_268293801_n.jpg
381 ms
12816975_1707528809522172_1579945234_n.jpg
379 ms
12797732_1529832590644850_1070432889_n.jpg
434 ms
12825785_766875940080147_494695649_n.jpg
410 ms
12725031_1696407403971364_1664384854_n.jpg
414 ms
12816941_1072407479482330_1107039677_n.jpg
461 ms
1739506_164176173971888_1623924053_n.jpg
399 ms
12822572_1686341954969367_298065565_n.jpg
434 ms
12822525_1000924556644446_799005410_n.jpg
433 ms
12783208_1733470336939254_2116505438_n.jpg
467 ms
12826241_1717296171844389_1800465869_n.jpg
511 ms
12797907_974293265952158_1021637740_n.jpg
449 ms
12826161_1722837004596384_244168186_n.jpg
451 ms
10467982_973943739356600_673653897_n.jpg
471 ms
12751507_1396031227371309_396624690_n.jpg
482 ms
12783931_1756365157932167_1918138181_n.jpg
468 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
126 ms
3193398744-postmessagerelay.js
92 ms
rpc:shindig_random.js
88 ms
collect
39 ms
collect
93 ms
stackpile.api-6712054ce0.js
36 ms
async-ads.js
49 ms
small-logo.png
40 ms
cb=gapi.loaded_0
6 ms
nr-885.min.js
45 ms
a53393d12f
46 ms
1170124_525281170988536_1939942753_n.jpg
172 ms
10598754_234107923601136_490095183_n.jpg
150 ms
1962959_389594164497743_1486795602_n.jpg
151 ms
12530854_1732239746997791_1162832666_n.jpg
146 ms
917287_1773512102880009_369441756_n.jpg
142 ms
10919209_486068841593474_1133264436_n.jpg
140 ms
12797937_767372833407349_1668982858_n.jpg
154 ms
12798129_1007198506022329_171542602_n.jpg
163 ms
12328423_851051205040388_264118629_n.jpg
142 ms
12751531_1734368960130508_1841562654_n.jpg
200 ms
12798127_1025171444219767_828711400_n.jpg
267 ms
12751356_901026976685139_1729195474_n.jpg
213 ms
12750039_841051109338268_1535776823_n.jpg
208 ms
12783202_1532654327035288_599596410_n.jpg
236 ms
12750081_882753728488763_1584309029_n.jpg
266 ms
12747759_560697834095759_1336173528_n.jpg
342 ms
12747792_1686982491558558_2088307766_n.jpg
325 ms
12816777_987486681339867_1549496663_n.jpg
271 ms
12797793_191719471197442_1246486859_n.jpg
292 ms
12822316_463324100519800_1546162793_n.jpg
318 ms
12446089_790097051134654_136731991_n.jpg
313 ms
12783505_349092408594400_403174956_n.jpg
358 ms
11355999_556856687799995_362847403_n.jpg
353 ms
12748432_1277512072275210_1858390544_n.jpg
383 ms
12728543_940839996012745_739607946_n.jpg
375 ms
12747791_966129843470753_519494788_n.jpg
458 ms
12728680_451571635037149_1273475168_n.jpg
465 ms
12716524_424190037790523_349720947_n.jpg
414 ms
12747576_175287719516979_2081481141_n.jpg
470 ms
12749960_1566124060345390_1295245272_n.jpg
675 ms
12716829_1560687844247741_970650715_n.jpg
465 ms
12783924_599257276890455_522096444_n.jpg
592 ms
12729469_146191659101332_1019307614_n.jpg
530 ms
bg.png
102 ms
play_small.png
104 ms
collect
96 ms
306752634-lightbox_bundle.css
7 ms
1blog2lives.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1blog2lives.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that 1blog2lives.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.
1blog2lives.com
Open Graph description is not detected on the main page of 1 Blog 2 Lives. 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: