Access lifebook.co.kr. 생명의 말씀을 밝히는 삶 [라이프북/생명의말씀사]

lifebook.co.kr screenshot

10

Performance

Renders faster than
23% of other websites
84

Accessibility

Visual factors better than
that of 57% of websites
58

Best Practices

More advanced features
available than in
19% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

683 ms

Resources Loaded

14.3 sec

Page Rendered

518 ms

lifebook.co.kr screenshot

About Website

Click here to check amazing Lifebook content for South Korea. Otherwise, check out these important facts you probably never knew about lifebook.co.kr

Visit lifebook.co.kr

Key Findings

We analyzed Lifebook.co.kr page load time and found that the first response time was 683 ms and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value15.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value40.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,610 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.203

61/100

15%

TTI (Time to Interactive)

Value36.8 s

0/100

10%

lifebook.co.kr

683 ms

index.html

902 ms

google_tracker.js

425 ms

jquery-1.9.1.min.js

1090 ms

jquery-ui.min.js

1406 ms

Our browser made a total of 295 requests to load all elements on the main page. We found that 99% of them (293 requests) were addressed to the original Lifebook.co.kr, 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Lifebook.co.kr.

Content Size

5.3 MB

After Optimization

4.5 MB

In fact, the total size of Lifebook.co.kr main page is 5.3 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. 55% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 242.6 kB

Original 279.6 kB
After minification 235.6 kB
After compression 37.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. This page needs HTML code to be minified as it can gain 44.0 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 242.6 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 170.8 kB

Original 4.5 MB
After minification 4.3 MB

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. Lifebook images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 302.9 kB

Original 427.6 kB
After minification 415.5 kB
After compression 124.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 302.9 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 47.1 kB

Original 58.4 kB
After minification 50.3 kB
After compression 11.3 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. Lifebook.co.kr needs all CSS files to be minified and compressed as it can save up to 47.1 kB or 81% of the original size.

Requests Now

292

After Optimization

249

The browser has sent 292 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifebook. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

KO
Language Claimed

N/A
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifebook.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Lifebook.co.kr main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lifebook.co.kr

Open Graph description is not detected on the main page of Lifebook. 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: