Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

corec.jp

無料で導入!BtoBクラウド受注・発注システム-コレック

Page Load Speed

3.5 sec in total

First Response

310 ms

Resources Loaded

2.9 sec

Page Rendered

208 ms

corec.jp screenshot

About Website

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

売り手は卸売の注文フォームを作成し、受注から納品書・請求書の作成までを簡単にWebで管理できるようになります。買い手は、仕入れや購買の発注書をPCやスマホで作成し、メールやFAX宛に送信できます。BtoBなのに無料で始められ、導入も簡単。業務効率化が進みます。 インボイス制度制度にも対応しています。

Visit corec.jp

Key Findings

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

Performance Metrics

corec.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

corec.jp

310 ms

corec.jp

617 ms

jquery-1.8.3.min-e318eee26a768a0b8aae050429a50682.js

297 ms

jquery.placeholder-574fddab80abc6725768ece72fe3a50c.js

434 ms

prelogin-32be00c95459ec374d229f6e4e01b225.js

434 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 95% of them (40 requests) were addressed to the original Corec.jp, 2% (1 request) were made to Cdn.optimizely.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Corec.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.4 kB (3%)

Content Size

938.9 kB

After Optimization

911.5 kB

In fact, the total size of Corec.jp main page is 938.9 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 826.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 13.3 kB

  • Original 18.2 kB
  • After minification 15.5 kB
  • After compression 4.9 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 2.7 kB, which is 15% 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 13.3 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 10.8 kB

  • Original 826.1 kB
  • After minification 815.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. Corec images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 219 B

  • Original 65.9 kB
  • After minification 65.9 kB
  • After compression 65.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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 3.1 kB

  • Original 28.7 kB
  • After minification 28.7 kB
  • After compression 25.6 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. Corec.jp needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (38%)

Requests Now

40

After Optimization

25

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Corec. 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 as a result speed up the page load time.

Accessibility Review

corec.jp accessibility score

75

Accessibility Issues

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 [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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

corec.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

SEO Factors

corec.jp SEO score

88

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corec.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Corec.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

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