3.5 sec in total
310 ms
2.9 sec
208 ms
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.jpWe 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.
corec.jp performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value9.1 s
1/100
25%
Value6.8 s
34/100
10%
Value670 ms
44/100
30%
Value0.003
100/100
15%
Value12.1 s
16/100
10%
310 ms
617 ms
297 ms
434 ms
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 size can be reduced by 27.4 kB (3%)
938.9 kB
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.
Potential reduce by 13.3 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.
Potential reduce by 10.8 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.
Potential reduce by 219 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. This website has mostly compressed JavaScripts.
Potential reduce by 3.1 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.
Number of requests can be reduced by 15 (38%)
40
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.
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
jquery.inputvalidation-16531192016fb21f9b76490b78182c50.js
434 ms
jquery.equalheight.min-b24d3ecf44dbcdd2e5be34d0e39f51fc.js
438 ms
jquery.responsiveslides-56a5d6bb437e48b74e30ae6433fd3ac5.js
440 ms
jquery.appear-d8c07df8531a7ce5cadb4f55003cc5fd.js
443 ms
reset.css
577 ms
common-ddcae2009b801af8d3963802996eb01b.css
578 ms
style-97ff1d67dc2ee8d57a805d00b9e2db72.css
722 ms
2239731971.js
33 ms
top-40fc7944b22e0b22e7fbfb9093d95d51.js
583 ms
gtm.js
176 ms
logo.png
216 ms
icon_login_gray.png
213 ms
img_main_01.jpg
644 ms
img_main_02.jpg
795 ms
img_main_03.jpg
799 ms
img_main_sp_01.jpg
499 ms
img_main_sp_02.jpg
643 ms
img_main_sp_03.jpg
508 ms
img_covered_texture.png
644 ms
img_main_illust.svg
657 ms
bg_top_building.jpg
790 ms
icon_top_achivement_01.png
788 ms
icon_top_achivement_02.png
789 ms
icon_top_achivement_03.png
803 ms
icon_top_achivement_04.png
932 ms
icon_top_achivement_05.png
933 ms
icon_top_achivement_06.png
932 ms
img_bl.png
940 ms
img_fb.png
945 ms
img_pagetop.png
950 ms
icon_wht_arrow_r_l.png
955 ms
icon_dmain_sd_l_gra.svg
956 ms
icon_dmain_co_l_gra.svg
956 ms
icon_dmain_sdf_l_gra.svg
965 ms
icon_dmain_pa_l_gra.svg
971 ms
icon_dmain_ur_l_gra.svg
976 ms
icon_dmain_rnt_l_gra.svg
1098 ms
corec.jp accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
corec.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
corec.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
N/A
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.
corec.jp
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: