7.7 sec in total
1.3 sec
6.2 sec
186 ms
Visit life-burn.com now to see the best up-to-date Life Burn content for Japan and also check out these interesting facts you probably never knew about life-burn.com
欢迎您
Visit life-burn.comWe analyzed Life-burn.com page load time and found that the first response time was 1.3 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
life-burn.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.0 s
6/100
25%
Value4.8 s
68/100
10%
Value110 ms
98/100
30%
Value0.166
71/100
15%
Value4.2 s
85/100
10%
1283 ms
1520 ms
3364 ms
6 ms
17 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 11% of them (3 requests) were addressed to the original Life-burn.com, 14% (4 requests) were made to Howcollect.cdn-donuts.jp and 7% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Life-burn.com.
Page size can be reduced by 604.0 kB (50%)
1.2 MB
606.2 kB
In fact, the total size of Life-burn.com main page is 1.2 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. Javascripts take 716.8 kB which makes up the majority of the site volume.
Potential reduce by 11.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 11.5 kB or 67% of the original size.
Potential reduce by 0 B
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. Life Burn images are well optimized though.
Potential reduce by 477.7 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 477.7 kB or 67% of the original size.
Potential reduce by 114.7 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. Life-burn.com needs all CSS files to be minified and compressed as it can save up to 114.7 kB or 82% of the original size.
Number of requests can be reduced by 3 (12%)
25
22
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Burn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
life-burn.com
1283 ms
application-14e356ff37b1c2334876cfe918fdc83e.css
1520 ms
application-25687d8b27280244c0cdbc7c5a7deb61.js
3364 ms
font-awesome.min.css
6 ms
advs-instream.js
17 ms
analytics.js
58 ms
20160315072122-3298-354_raw.jpg
837 ms
239.jpg
810 ms
3-1-10.png
81 ms
267b2_137_423eadf8_913a7cae-m.jpg
767 ms
E1412242289114_6.jpg
177 ms
7d370bd2e108d09a4de273ae1b64d64c852d902a.72.2.9.2.jpeg
1180 ms
aaaaaaaaaaaaaa-300x200.jpg
641 ms
1-19.41.23.jpg
472 ms
a7c37aee-s.jpg
1117 ms
yayt.jpg
742 ms
images
77 ms
0311_8.png
645 ms
20160314042026-3298-754_raw.jpg
675 ms
20130201011503-838-719_raw.jpg
840 ms
20160311074522-3298-955_raw.jpg
823 ms
all.js
43 ms
fontawesome-webfont.woff
12 ms
collect
19 ms
167 ms
xd_arbiter.php
21 ms
xd_arbiter.php
32 ms
1-19.41.23.jpg
1184 ms
life-burn.com accessibility score
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
Image elements do not have [alt] attributes
life-burn.com 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
General
Impact
Issue
Browser errors were logged to the console
life-burn.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Life-burn.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 Japanese. Our system also found out that Life-burn.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.
life-burn.com
Open Graph description is not detected on the main page of Life Burn. 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: