Tools & Wizards About Us
app-j.com screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

app-j.com

APPJ(エイピーピー・ジャパン株式会社) | 製紙メーカーAPP

Page Load Speed

23.9 sec in total

First Response

928 ms

Resources Loaded

22.9 sec

Page Rendered

90 ms

app-j.com screenshot

About Website

Visit app-j.com now to see the best up-to-date APPJ content for Japan and also check out these interesting facts you probably never knew about app-j.com

アジアを拠点としたグローバルな総合製紙メーカー、エイピーピー・ジャパン(株)のWebサイトです。雑誌や書籍向けの印刷用紙や情報用紙、包装用紙、段ボールや紙器などに用いられる板紙・原紙等お探しの方はお問合せください。

Visit app-j.com

Key Findings

We analyzed App-j.com page load time and found that the first response time was 928 ms and then it took 22.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

app-j.com performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

app-j.com

928 ms

js

72 ms

import_home.css

335 ms

jquery.js

1180 ms

smoothscroll.js

347 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 85% of them (35 requests) were addressed to the original App-j.com, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Adobe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.4 kB (42%)

Content Size

201.7 kB

After Optimization

117.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of App-j.com main page is 201.7 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. 15% of websites need less resources to load. Javascripts take 127.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.9 kB

  • Original 11.1 kB
  • After minification 10.2 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 7.9 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 699 B

  • Original 43.2 kB
  • After minification 42.5 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. APPJ images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 60.6 kB

  • Original 127.9 kB
  • After minification 125.1 kB
  • After compression 67.3 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 60.6 kB or 47% of the original size.

CSS Optimization

-78%

Potential reduce by 15.2 kB

  • Original 19.6 kB
  • After minification 14.9 kB
  • After compression 4.3 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. App-j.com needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (26%)

Requests Now

38

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

app-j.com

app-j.com

928 ms

js

js

72 ms

import_home.css

import_home.css

335 ms

jquery.js

jquery.js

1180 ms

smoothscroll.js

smoothscroll.js

347 ms

rollover.js

rollover.js

348 ms

css_browser_selector.js

css_browser_selector.js

391 ms

jsapi

jsapi

23 ms

loader.js

loader.js

19 ms

reset.css

reset.css

348 ms

base.css

base.css

672 ms

second.css

second.css

813 ms

home.css

home.css

394 ms

get_flash_player.gif

get_flash_player.gif

20468 ms

header_bg.jpg

header_bg.jpg

176 ms

logo.jpg

logo.jpg

811 ms

btn_twitter01.gif

btn_twitter01.gif

326 ms

h_contact.jpg

h_contact.jpg

340 ms

gnav01.gif

gnav01.gif

509 ms

gnav02.gif

gnav02.gif

549 ms

gnav03.gif

gnav03.gif

665 ms

gnav04.gif

gnav04.gif

831 ms

gnav05.gif

gnav05.gif

863 ms

gnav06.gif

gnav06.gif

1015 ms

left_menu01.jpg

left_menu01.jpg

1041 ms

left_menu03.jpg

left_menu03.jpg

1005 ms

left_menu04.jpg

left_menu04.jpg

1300 ms

left_menu05.jpg

left_menu05.jpg

1348 ms

f_logo.jpg

f_logo.jpg

1364 ms

btn_twitter02.gif

btn_twitter02.gif

1344 ms

li_blog.jpg

li_blog.jpg

1342 ms

icon.jpg

icon.jpg

1357 ms

footer_back.jpg

footer_back.jpg

1603 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

12 ms

gnav01_o.gif

gnav01_o.gif

494 ms

gnav02_o.gif

gnav02_o.gif

493 ms

gnav03_o.gif

gnav03_o.gif

510 ms

gnav04_o.gif

gnav04_o.gif

511 ms

gnav05_o.gif

gnav05_o.gif

517 ms

gnav06_o.gif

gnav06_o.gif

533 ms

Accessibility Review

app-j.com accessibility score

63

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

app-j.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

app-j.com SEO score

69

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

Document uses plugins

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 App-j.com 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 App-j.com 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

app-j.com

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