Tools & Wizards About Us
lpi.or.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

lpi.or.jp

IT資格といえば LPI-Japan | LinuC/OSS-DB/HTML5/OPCEL

Page Load Speed

9.6 sec in total

First Response

549 ms

Resources Loaded

7.4 sec

Page Rendered

1.7 sec

lpi.or.jp screenshot

About Website

Visit lpi.or.jp now to see the best up-to-date LPI content for Japan and also check out these interesting facts you probably never knew about lpi.or.jp

Linux/OSS技術者のスキルを認定するLPI-Japanの公式サイト。LinuC（Linux）、OSS-DB（PostgreSQL）、HTML5、OPCEL（OpenStack）、LinuCに関する無料セミナー、例題解説、教科書の無料ダウンロードなど、学習に役立つコンテンツが満載。クラウド時代におけるIT技術者必見情報が満載

Visit lpi.or.jp

Key Findings

We analyzed Lpi.or.jp page load time and found that the first response time was 549 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lpi.or.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.425

22/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

lpi.or.jp

549 ms

lpi.or.jp

1424 ms

swiper.min.css

42 ms

css

46 ms

css

60 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 87% of them (104 requests) were addressed to the original Lpi.or.jp, 3% (3 requests) were made to Cdnjs.cloudflare.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Lpi.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 517.9 kB (8%)

Content Size

6.6 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lpi.or.jp main page is 6.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 152.7 kB

  • Original 168.2 kB
  • After minification 106.7 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 61.4 kB, which is 37% 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 152.7 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 297.6 kB

  • Original 6.3 MB
  • After minification 6.0 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. LPI images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 9.7 kB

  • Original 62.9 kB
  • After minification 58.3 kB
  • After compression 53.2 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 9.7 kB or 15% of the original size.

CSS Optimization

-73%

Potential reduce by 58.0 kB

  • Original 79.4 kB
  • After minification 62.7 kB
  • After compression 21.5 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. Lpi.or.jp needs all CSS files to be minified and compressed as it can save up to 58.0 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (16%)

Requests Now

116

After Optimization

97

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lpi.or.jp

lpi.or.jp

549 ms

lpi.or.jp

lpi.or.jp

1424 ms

swiper.min.css

swiper.min.css

42 ms

css

css

46 ms

css

css

60 ms

all.css

all.css

41 ms

style.css

style.css

1060 ms

jquery.min.js

jquery.min.js

18 ms

swiper.min.js

swiper.min.js

13 ms

jquery.cookie.js

jquery.cookie.js

19 ms

script.js

script.js

176 ms

gtm.js

gtm.js

242 ms

linuc_logomark.jpg

linuc_logomark.jpg

370 ms

logo.png

logo.png

370 ms

twitter.png

twitter.png

513 ms

search.png

search.png

521 ms

search_g.png

search_g.png

689 ms

i_menu01.png

i_menu01.png

692 ms

i_menu02.png

i_menu02.png

698 ms

i_menu03.png

i_menu03.png

710 ms

i_menu04.png

i_menu04.png

714 ms

i_menu05.png

i_menu05.png

715 ms

i_menu06.png

i_menu06.png

863 ms

i_menu07.png

i_menu07.png

867 ms

right_arrow_white.png

right_arrow_white.png

875 ms

menu_support02_icon01.png

menu_support02_icon01.png

895 ms

right_arrow_blue.png

right_arrow_blue.png

900 ms

menu_support02_icon02.png

menu_support02_icon02.png

901 ms

menu_support02_icon03.png

menu_support02_icon03.png

1038 ms

menu_support02_icon04.png

menu_support02_icon04.png

1044 ms

menu_support02_icon05.png

menu_support02_icon05.png

1051 ms

menu_support02_icon06.png

menu_support02_icon06.png

1082 ms

menu_support02_icon07.png

menu_support02_icon07.png

1088 ms

twitter_wh.png

twitter_wh.png

1089 ms

search_wh.png

search_wh.png

1213 ms

mv01.jpg

mv01.jpg

4041 ms

mv_ttl.png

mv_ttl.png

1932 ms

mv01_sp.jpg

mv01_sp.jpg

2382 ms

mv_ttl_sp.png

mv_ttl_sp.png

1836 ms

linuc.png

linuc.png

1275 ms

html_logo.png

html_logo.png

1388 ms

ossdb_logo.png

ossdb_logo.png

1464 ms

openstack_logo.png

openstack_logo.png

1739 ms

k8s_logo.png

k8s_logo.png

1652 ms

bnr25.png

bnr25.png

2213 ms

bnr26.png

bnr26.png

2438 ms

bnr20.png

bnr20.png

2024 ms

support01_mvbg.png

support01_mvbg.png

2856 ms

font

font

76 ms

font

font

77 ms

fa-brands-400.woff

fa-brands-400.woff

59 ms

index.js

index.js

264 ms

support01_icon01.png

support01_icon01.png

1848 ms

js

js

62 ms

analytics.js

analytics.js

22 ms

support01_icon02.png

support01_icon02.png

2005 ms

collect

collect

66 ms

collect

collect

30 ms

support01_icon03.png

support01_icon03.png

1894 ms

support01_icon04.png

support01_icon04.png

2052 ms

support02_icon01.png

support02_icon01.png

1905 ms

support02_icon04.png

support02_icon04.png

1903 ms

support02_icon02.png

support02_icon02.png

1920 ms

support02_icon05.png

support02_icon05.png

2049 ms

support02_icon03.png

support02_icon03.png

2066 ms

support02_icon09.png

support02_icon09.png

2067 ms

support02_icon06.png

support02_icon06.png

1930 ms

support02_icon07.png

support02_icon07.png

2079 ms

support03_image01.jpg

support03_image01.jpg

2281 ms

support03_image06.jpg

support03_image06.jpg

2073 ms

support03_image02.jpg

support03_image02.jpg

2069 ms

support03_image03.jpg

support03_image03.jpg

2231 ms

support03_image04.jpg

support03_image04.jpg

2306 ms

support03_image05.jpg

support03_image05.jpg

2101 ms

support03_image07.jpg

support03_image07.jpg

2118 ms

support01_mvmodel.png

support01_mvmodel.png

3538 ms

examinee12.jpg

examinee12.jpg

2231 ms

examinee13.jpg

examinee13.jpg

2254 ms

examinee11.jpg

examinee11.jpg

2132 ms

examinee09.jpg

examinee09.jpg

2221 ms

examinee05.jpg

examinee05.jpg

2142 ms

recommend_company30.jpg

recommend_company30.jpg

2067 ms

recommend_company29.jpg

recommend_company29.jpg

1871 ms

recommend_company23.jpg

recommend_company23.jpg

2107 ms

recommend_company15.jpg

recommend_company15.jpg

1863 ms

recommend_company04.jpg

recommend_company04.jpg

1785 ms

recommend_company06.jpg

recommend_company06.jpg

1880 ms

lpi-bg.png

lpi-bg.png

1664 ms

eco_spo.png

eco_spo.png

1693 ms

eco_spo_sp.png

eco_spo_sp.png

1637 ms

eco_ac.png

eco_ac.png

1652 ms

eco_ac_sp.png

eco_ac_sp.png

1692 ms

eco_comu.png

eco_comu.png

1656 ms

eco_comu_sp.png

eco_comu_sp.png

1627 ms

eco_ins.png

eco_ins.png

1627 ms

eco_ins_sp.png

eco_ins_sp.png

1640 ms

eco_biz.png

eco_biz.png

1667 ms

eco_biz_sp.png

eco_biz_sp.png

1527 ms

lpi-circle.png

lpi-circle.png

1596 ms

atlink.png

atlink.png

1617 ms

citrix.png

citrix.png

1618 ms

cm.png

cm.png

1527 ms

cybertrust.png

cybertrust.png

1504 ms

designet.png

designet.png

1580 ms

embex.png

embex.png

1583 ms

fujitsu.png

fujitsu.png

1456 ms

gospa.png

gospa.png

1517 ms

hitachi.png

hitachi.png

1507 ms

isfnet.png

isfnet.png

1558 ms

kenschool.png

kenschool.png

1431 ms

leading-edge.png

leading-edge.png

1422 ms

minebea.png

minebea.png

1464 ms

nec.png

nec.png

1503 ms

nec-solution.png

nec-solution.png

1353 ms

technology.png

technology.png

1379 ms

ping-t.png

ping-t.png

1397 ms

reskill.png

reskill.png

1408 ms

solcreo.png

solcreo.png

1292 ms

zeus.png

zeus.png

1317 ms

logo_green.png

logo_green.png

1191 ms

Accessibility Review

lpi.or.jp accessibility score

95

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.

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

Links do not have a discernible name

Best Practices

lpi.or.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lpi.or.jp SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lpi.or.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 Lpi.or.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

lpi.or.jp

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