Tools & Wizards About Us
lifelist.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

lifelist.jp

よく使うサイトをブックマーク表示できるPCサイト - ライフリスト(LifeList.jp)

Page Load Speed

3 sec in total

First Response

969 ms

Resources Loaded

1.8 sec

Page Rendered

196 ms

lifelist.jp screenshot

About Website

Welcome to lifelist.jp homepage info - get ready to check Life List best content for Japan right away, or after learning these important things about lifelist.jp

よく使うサイトをブックマーク表示できるPCサイトです。ライフリスト(LifeList)でPCのブラウザ ブックマークをショートカット。パソコンでよく使うサイトを簡単にブックマーク表示する方法でもお馴染みのシンプルなPC専用テキストブックマークです。LifeList(ライフリスト)はシンプルなDIYリンク集だからPCブラウザのブックマークショートカットに最適！アナログ表示のPC用よく使うサイトをブッ...

Visit lifelist.jp

Key Findings

We analyzed Lifelist.jp page load time and found that the first response time was 969 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

lifelist.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

lifelist.jp

969 ms

01_special_01_0030.css

862 ms

img111.gif

354 ms

ir

155 ms

jquery-ui.css

63 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 35% of them (6 requests) were addressed to the original Lifelist.jp, 29% (5 requests) were made to Ajax.googleapis.com and 12% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (969 ms) belongs to the original domain Lifelist.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.0 kB (71%)

Content Size

122.0 kB

After Optimization

35.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifelist.jp main page is 122.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 53.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 28.0 kB

  • Original 33.1 kB
  • After minification 26.1 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 21% 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 28.0 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 180 B

  • Original 4.5 kB
  • After minification 4.3 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. Life List images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 31.2 kB

  • Original 53.8 kB
  • After minification 32.1 kB
  • After compression 22.5 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 31.2 kB or 58% of the original size.

CSS Optimization

-90%

Potential reduce by 27.6 kB

  • Original 30.7 kB
  • After minification 27.7 kB
  • After compression 3.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. Lifelist.jp needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (40%)

Requests Now

15

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lifelist.jp

lifelist.jp

969 ms

01_special_01_0030.css

01_special_01_0030.css

862 ms

img111.gif

img111.gif

354 ms

ir

ir

155 ms

jquery-ui.css

jquery-ui.css

63 ms

jsapi

jsapi

47 ms

jquery.upload-1.0.2.fix.js

jquery.upload-1.0.2.fix.js

188 ms

json2.js

json2.js

352 ms

my-favorites.js

my-favorites.js

697 ms

1x1.gif

1x1.gif

408 ms

ga.js

ga.js

31 ms

jquery.min.js

jquery.min.js

31 ms

jquery-ui.min.js

jquery-ui.min.js

45 ms

__utm.gif

__utm.gif

38 ms

collect

collect

65 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

53 ms

ui-icons_469bdd_256x240.png

ui-icons_469bdd_256x240.png

32 ms

Accessibility Review

lifelist.jp accessibility score

68

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

lifelist.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lifelist.jp SEO score

67

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifelist.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Lifelist.jp main page’s claimed encoding is shift_jis. 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

lifelist.jp

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