Tools & Wizards About Us
l--l.jp screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

l--l.jp

無料レンタルCGI【PIERROT】　-　占い/検索エンジン/リンク集/日記/スケジュール帳/掲示板/チャット/アフィリエイト/アクセス解析

Page Load Speed

3.8 sec in total

First Response

530 ms

Resources Loaded

3.1 sec

Page Rendered

166 ms

l--l.jp screenshot

About Website

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

無料レンタルCGI【各種占い(22種)/検索エンジン/アクセス解析/スケジュール/メールフォーム/相互リンク/グーグルマップ/ストリートビュー/画像日記/ホームページバトル/掲示板/チャット/投票/自動リンク/用語集/アフィリエイト】でホームページにアクセントを！

Visit l--l.jp

Key Findings

We analyzed L--l.jp page load time and found that the first response time was 530 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

l--l.jp performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

l--l.jp

530 ms

l--l.jp

1023 ms

style.css

353 ms

bombstrap.css

1298 ms

0.gif

687 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 84% of them (27 requests) were addressed to the original L--l.jp, 6% (2 requests) were made to Noface.jp and 3% (1 request) were made to Www12.a8.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain L--l.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.4 kB (80%)

Content Size

188.8 kB

After Optimization

37.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of L--l.jp main page is 188.8 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. Only 10% of websites need less resources to load. CSS take 141.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 31.0 kB

  • Original 36.6 kB
  • After minification 25.1 kB
  • After compression 5.7 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 11.6 kB, which is 32% 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 31.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 6 B

  • Original 7.5 kB
  • After minification 7.5 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. L images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 2.1 kB

  • Original 3.1 kB
  • After minification 2.3 kB
  • After compression 929 B

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 2.1 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 118.3 kB

  • Original 141.6 kB
  • After minification 116.2 kB
  • After compression 23.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. L--l.jp needs all CSS files to be minified and compressed as it can save up to 118.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (70%)

Requests Now

30

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

l--l.jp

l--l.jp

530 ms

l--l.jp

l--l.jp

1023 ms

style.css

style.css

353 ms

bombstrap.css

bombstrap.css

1298 ms

0.gif

0.gif

687 ms

item.gif

item.gif

527 ms

rank1.gif

rank1.gif

535 ms

rank2.gif

rank2.gif

535 ms

rank3.gif

rank3.gif

564 ms

rank4.gif

rank4.gif

564 ms

rank5.gif

rank5.gif

706 ms

new.gif

new.gif

711 ms

calendar.png

calendar.png

545 ms

search.png

search.png

584 ms

chat.png

chat.png

584 ms

diary.png

diary.png

711 ms

uranai.png

uranai.png

718 ms

pop.png

pop.png

721 ms

board.png

board.png

771 ms

mailform.png

mailform.png

771 ms

free.png

free.png

886 ms

vote.png

vote.png

893 ms

kantei.png

kantei.png

897 ms

special.png

special.png

962 ms

b2.gif

b2.gif

962 ms

b1.gif

b1.gif

1059 ms

b3.gif

b3.gif

1067 ms

b5.gif

b5.gif

1073 ms

bgt

bgt

1009 ms

0.gif

0.gif

671 ms

in.js

in.js

864 ms

in.cgi

in.cgi

325 ms

Accessibility Review

l--l.jp accessibility score

65

Accessibility Issues

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a valid value for its [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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

l--l.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

l--l.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JP

  • Encoding

    UTF-8

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

Social Sharing Optimization

l--l.jp

Open Graph data is detected on the main page of L. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: