11.2 sec in total
2.9 sec
7.4 sec
772 ms
Click here to check amazing Lificcase content. Otherwise, check out these important facts you probably never knew about lificcase.com
text/html; charset=utf-8
Visit lificcase.comWe analyzed Lificcase.com page load time and found that the first response time was 2.9 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lificcase.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.8 s
15/100
25%
Value10.0 s
9/100
10%
Value10 ms
100/100
30%
Value0.005
100/100
15%
Value8.6 s
37/100
10%
2949 ms
388 ms
62 ms
72 ms
84 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 60% of them (55 requests) were addressed to the original Lificcase.com, 12% (11 requests) were made to I2.wp.com and 8% (7 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Lificcase.com.
Page size can be reduced by 1.8 MB (22%)
8.1 MB
6.3 MB
In fact, the total size of Lificcase.com main page is 8.1 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. 60% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.0 kB or 84% of the original size.
Potential reduce by 5.7 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. Lificcase images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 79% of the original size.
Potential reduce by 658.1 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. Lificcase.com needs all CSS files to be minified and compressed as it can save up to 658.1 kB or 87% of the original size.
Number of requests can be reduced by 51 (60%)
85
34
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lificcase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
lificcase.com
2949 ms
wp-emoji-release.min.js
388 ms
css
62 ms
css
72 ms
css
84 ms
css
92 ms
styles.css
390 ms
sb-instagram.css
392 ms
font-awesome.min.css
248 ms
rgs.css
391 ms
font-awesome.min.css
393 ms
style.css
961 ms
responsive.css
790 ms
widget.css
606 ms
js_composer.css
798 ms
jetpack.css
707 ms
jquery.js
996 ms
jquery-migrate.min.js
809 ms
modernizr.js
904 ms
core.min.js
551 ms
widget.min.js
555 ms
position.min.js
735 ms
menu.min.js
736 ms
autocomplete.min.js
749 ms
wpss-search-suggest.js
756 ms
photon.js
755 ms
jquery.form.min.js
757 ms
scripts.js
701 ms
sb-instagram.js
793 ms
devicepx-jetpack.js
7 ms
gprofiles.js
63 ms
wpgroho.js
842 ms
respond.js
866 ms
sticky.js
880 ms
prettyPhoto.js
882 ms
isotope.min.js
1089 ms
superfish.js
987 ms
init.js
1422 ms
nectar-slider.js
1264 ms
vivus.min.js
1084 ms
comment-reply.min.js
1097 ms
wp-embed.min.js
1183 ms
js_composer_front.js
1284 ms
e-201611.js
4 ms
css
31 ms
nanumgothic.css
35 ms
logo1_h24.png
97 ms
logo1_white.png
96 ms
i_2.png
1749 ms
logo11.png
65 ms
i_3.png
1726 ms
i_4.png
1723 ms
i_5.png
1723 ms
mcd_n5.jpg
65 ms
mcd_ip6.jpg
63 ms
mcd_ip6plus.jpg
64 ms
saffiano_n5.jpg
64 ms
saffiano_edgeplus.jpg
66 ms
saffiano_a8.jpg
68 ms
saffiano_n4.jpg
65 ms
saffiano_ip6plus1.jpg
66 ms
saffiano_g41.jpg
62 ms
saffiano_ip6.jpg
65 ms
transparent.png
703 ms
map_bg.png
2139 ms
i_1.png
1718 ms
mcd_edplus.jpg
66 ms
mcd_s6ed.jpg
65 ms
mcd_s6.jpg
66 ms
saffiano_s6.jpg
67 ms
OpenSans-Regular-webfont.woff
606 ms
OpenSans-Light-webfont.woff
700 ms
OpenSans-Semibold-webfont.woff
787 ms
OpenSansBold-webfont.woff
1673 ms
icomoon.woff
808 ms
g.gif
814 ms
hovercard.css
672 ms
services.css
672 ms
diagonal_line.png
233 ms
1903x983_5.jpg
1342 ms
1903x983_6.jpg
1726 ms
1903x983_2.jpg
1367 ms
1903x983.jpg
1742 ms
saffiano_diary.jpg
2128 ms
nectar-loading.gif
392 ms
basic_paperplane.svg
506 ms
ecommerce_receipt_dollar.svg
700 ms
basic_elaboration_tablet_pencil.svg
894 ms
basic_share.svg
1088 ms
basic_bolt.svg
1282 ms
music_shuffle_button.svg
1445 ms
lificcase.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Links do not have a discernible name
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.
lificcase.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
Detected JavaScript libraries
Browser errors were logged to the console
lificcase.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
ZH
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lificcase.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed Korean language. Our system also found out that Lificcase.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.
lificcase.com
Open Graph data is detected on the main page of Lificcase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: