Tools & Wizards About Us
ashton.jp screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ashton.jp

International Corporate Communications | Ashton Consulting | Japan 日本

Page Load Speed

2.1 sec in total

First Response

51 ms

Resources Loaded

2 sec

Page Rendered

55 ms

ashton.jp screenshot

About Website

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

Ashton Consulting is Japan’s leading international corporate communications agency. Our bilingual professionals are experts on Japanese media, consumer and investor communities.

Visit ashton.jp

Key Findings

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

Performance Metrics

ashton.jp performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

www.ashton.jp

51 ms

minified.js

59 ms

focus-within-polyfill.js

57 ms

polyfill.min.js

811 ms

thunderbolt-commons.81e79c4a.bundle.min.js

86 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ashton.jp, 40% (14 requests) were made to Static.parastorage.com and 31% (11 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (811 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

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

Content Size

634.1 kB

After Optimization

367.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ashton.jp main page is 634.1 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. 45% of websites need less resources to load. HTML takes 352.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 260.1 kB

  • Original 352.7 kB
  • After minification 350.9 kB
  • After compression 92.6 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 260.1 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 2.5 kB

  • Original 36.5 kB
  • After minification 34.0 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. Ashton images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.2 kB

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

Requests Breakdown

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

Requests Now

32

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ashton.jp

www.ashton.jp

51 ms

minified.js

minified.js

59 ms

focus-within-polyfill.js

focus-within-polyfill.js

57 ms

polyfill.min.js

polyfill.min.js

811 ms

thunderbolt-commons.81e79c4a.bundle.min.js

thunderbolt-commons.81e79c4a.bundle.min.js

86 ms

main.e8bb44c8.bundle.min.js

main.e8bb44c8.bundle.min.js

87 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

86 ms

lodash.min.js

lodash.min.js

86 ms

react.production.min.js

react.production.min.js

85 ms

react-dom.production.min.js

react-dom.production.min.js

87 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

74 ms

40de1d_39d89ecbfec149c6820d7639e2c5781c~mv2_d_1215_1679_s_2.jpg

40de1d_39d89ecbfec149c6820d7639e2c5781c~mv2_d_1215_1679_s_2.jpg

270 ms

40de1d_7afbee3474be40d0bd1e2a24dbeaefdf~mv2.png

40de1d_7afbee3474be40d0bd1e2a24dbeaefdf~mv2.png

515 ms

40de1d_ebfd61c6b7014cd4824079c795bfa01e~mv2.png

40de1d_ebfd61c6b7014cd4824079c795bfa01e~mv2.png

456 ms

40de1d_681244e37bdb4194883ab81e7e551ac3~mv2.png

40de1d_681244e37bdb4194883ab81e7e551ac3~mv2.png

273 ms

40de1d_a8546fa7df2b4a44b1e3a180a2c42864~mv2.png

40de1d_a8546fa7df2b4a44b1e3a180a2c42864~mv2.png

542 ms

40de1d_b986b32956ac466eb9cb5ab35d7614ab~mv2.png

40de1d_b986b32956ac466eb9cb5ab35d7614ab~mv2.png

477 ms

bundle.min.js

bundle.min.js

35 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

35 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

35 ms

101 ms

96 ms

93 ms

94 ms

92 ms

92 ms

129 ms

131 ms

129 ms

127 ms

128 ms

deprecation-ja.v5.html

deprecation-ja.v5.html

5 ms

bolt-performance

bolt-performance

25 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

3 ms

Accessibility Review

ashton.jp accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

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

High

Page has valid source maps

SEO Factors

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ashton.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Ashton.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

ashton.jp

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