Tools & Wizards About Us
effigent.jp screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

effigent.jp

エフィジェント | リテールシステムパートナー

Page Load Speed

3.3 sec in total

First Response

725 ms

Resources Loaded

2.4 sec

Page Rendered

199 ms

effigent.jp screenshot

About Website

Visit effigent.jp now to see the best up-to-date Effigent content and also check out these interesting facts you probably never knew about effigent.jp

リテールシステムパートナー

Visit effigent.jp

Key Findings

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

Performance Metrics

effigent.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.566

12/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

effigent.jp

725 ms

import.css

288 ms

jquery.js

773 ms

share.js

539 ms

default.css

147 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 81% of them (35 requests) were addressed to the original Effigent.jp, 9% (4 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (922 ms) belongs to the original domain Effigent.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 172.0 kB (69%)

Content Size

251.0 kB

After Optimization

78.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Effigent.jp main page is 251.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. 35% of websites need less resources to load. Images take 147.0 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 6.1 kB

  • Original 9.3 kB
  • After minification 9.0 kB
  • After compression 3.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. 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 6.1 kB or 66% of the original size.

Image Optimization

-64%

Potential reduce by 94.7 kB

  • Original 147.0 kB
  • After minification 52.2 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. Obviously, Effigent needs image optimization as it can save up to 94.7 kB or 64% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 46.2 kB

  • Original 64.9 kB
  • After minification 61.8 kB
  • After compression 18.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 46.2 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 24.9 kB

  • Original 29.8 kB
  • After minification 19.9 kB
  • After compression 4.9 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. Effigent.jp needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (41%)

Requests Now

41

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

effigent.jp

effigent.jp

725 ms

import.css

import.css

288 ms

jquery.js

jquery.js

773 ms

share.js

share.js

539 ms

default.css

default.css

147 ms

style.css

style.css

546 ms

module.css

module.css

292 ms

bg_body.gif

bg_body.gif

174 ms

logo3.png

logo3.png

368 ms

catchphrase.png

catchphrase.png

185 ms

bg_nav.gif

bg_nav.gif

167 ms

nav_toppage.gif

nav_toppage.gif

171 ms

nav_service.gif

nav_service.gif

291 ms

nav_style.gif

nav_style.gif

629 ms

nav_result.gif

nav_result.gif

310 ms

nav_alliance.gif

nav_alliance.gif

562 ms

nav_company.gif

nav_company.gif

366 ms

nav_recruit.gif

nav_recruit.gif

435 ms

bg_contents.gif

bg_contents.gif

462 ms

bg_eye.gif

bg_eye.gif

606 ms

IMG_4078.jpg

IMG_4078.jpg

563 ms

eye_text.gif

eye_text.gif

605 ms

bg_ttl.gif

bg_ttl.gif

626 ms

media.gif

media.gif

713 ms

logo_itmedia.gif

logo_itmedia.gif

745 ms

insightnow_logo.jpg

insightnow_logo.jpg

745 ms

atmarkit_logo.gif

atmarkit_logo.gif

733 ms

isoms_200603_2.jpg

isoms_200603_2.jpg

764 ms

anken2.jpg

anken2.jpg

766 ms

growth.gif

growth.gif

879 ms

pagetop.gif

pagetop.gif

878 ms

copyright.gif

copyright.gif

922 ms

widgets.js

widgets.js

78 ms

glue_footer.gif

glue_footer.gif

846 ms

logo3_over.png

logo3_over.png

847 ms

nav_toppage_over.gif

nav_toppage_over.gif

847 ms

timeline.5d8406ab2e764a871ed41bd9aa0b693f.js

timeline.5d8406ab2e764a871ed41bd9aa0b693f.js

131 ms

syndication

syndication

124 ms

585781723876593665

585781723876593665

149 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

28 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

100 ms

Twitter_IMG_4188_normal.jpg

Twitter_IMG_4188_normal.jpg

194 ms

jot

jot

26 ms

Accessibility Review

effigent.jp accessibility score

97

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 input fields do not have accessible names

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

effigent.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

effigent.jp SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

effigent.jp

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