Tools & Wizards About Us
axc.jp screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

axc.jp

【あくせすぱーく】証書・賞状、会議録、論文、小部数製本、DM、電子化・スキャニング

Page Load Speed

3.5 sec in total

First Response

529 ms

Resources Loaded

2.8 sec

Page Rendered

162 ms

axc.jp screenshot

About Website

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

証書・賞状、会議録、論文、小部数製本、DMの専門サイトを運営。ご要望に合わせた商品をご提案。どうぞお気軽にお問い合わせ下さい。

Visit axc.jp

Key Findings

We analyzed Axc.jp page load time and found that the first response time was 529 ms and then it took 2.9 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

axc.jp performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

axc.jp

529 ms

a_design.css

169 ms

a1_user.css

349 ms

AC_RunActiveContent.js

335 ms

common.css

189 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 96% of them (43 requests) were addressed to the original Axc.jp, 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Axc.jp.

Page Optimization Overview & Recommendations

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

Content Size

482.4 kB

After Optimization

444.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 17.4 kB

  • Original 23.8 kB
  • After minification 22.5 kB
  • After compression 6.4 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 17.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 37 B

  • Original 434.2 kB
  • After minification 434.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. Axc images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 6.7 kB

  • Original 8.3 kB
  • After minification 5.2 kB
  • After compression 1.6 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 6.7 kB or 81% of the original size.

CSS Optimization

-87%

Potential reduce by 14.0 kB

  • Original 16.1 kB
  • After minification 5.4 kB
  • After compression 2.0 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. Axc.jp needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (20%)

Requests Now

44

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

axc.jp

axc.jp

529 ms

a_design.css

a_design.css

169 ms

a1_user.css

a1_user.css

349 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

335 ms

common.css

common.css

189 ms

textsettings.css

textsettings.css

329 ms

acclog.cgi

acclog.cgi

233 ms

bg_dot.gif

bg_dot.gif

170 ms

logo.gif

logo.gif

178 ms

bt_toi.gif

bt_toi.gif

173 ms

im_telno.gif

im_telno.gif

338 ms

newaxcpark.jpg

newaxcpark.jpg

1738 ms

bt_ss.gif

bt_ss.gif

332 ms

bt_ks.gif

bt_ks.gif

358 ms

bt_giji.gif

bt_giji.gif

348 ms

bt_th.gif

bt_th.gif

399 ms

bt_mb.gif

bt_mb.gif

490 ms

bt_scan.gif

bt_scan.gif

505 ms

bt_in.gif

bt_in.gif

519 ms

bt_guide.gif

bt_guide.gif

528 ms

kadobg01.gif

kadobg01.gif

565 ms

bt_annai.jpg

bt_annai.jpg

651 ms

kadobg02.gif

kadobg02.gif

672 ms

im_scon.gif

im_scon.gif

689 ms

sb_syousyo.gif

sb_syousyo.gif

698 ms

sb_kaku.gif

sb_kaku.gif

733 ms

sb_kaigiroku.gif

sb_kaigiroku.gif

810 ms

sb_ronbun.gif

sb_ronbun.gif

840 ms

sb_sho.gif

sb_sho.gif

859 ms

sb_scan.gif

sb_scan.gif

868 ms

sb_for.jpg

sb_for.jpg

900 ms

scon_bg.gif

scon_bg.gif

968 ms

bt_sakuin.jpg

bt_sakuin.jpg

1007 ms

b_ba_axctown.gif

b_ba_axctown.gif

1030 ms

im_new.gif

im_new.gif

1039 ms

b_ba_onayami.gif

b_ba_onayami.gif

1068 ms

b_ba_cpsite.jpg

b_ba_cpsite.jpg

1128 ms

b_ba_acpablog.gif

b_ba_acpablog.gif

1176 ms

international.gif

international.gif

1201 ms

ja_follow_me-a.jpg

ja_follow_me-a.jpg

1209 ms

twinavi_logo_88_31.jpg

twinavi_logo_88_31.jpg

1233 ms

back.jpg

back.jpg

1270 ms

all.js

all.js

14 ms

all.js

all.js

5 ms

footer.gif

footer.gif

1180 ms

Accessibility Review

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

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

axc.jp best practices score

75

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

axc.jp SEO score

67

Search Engine Optimization Advices

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

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

axc.jp

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