Tools & Wizards About Us
alexis.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

alexis.jp

株式会社 アレクシス -中国語、韓国語他、多言語の翻訳やDTP・WEB制作を扱う東京都内の翻訳会社

Page Load Speed

3.5 sec in total

First Response

743 ms

Resources Loaded

2.6 sec

Page Rendered

164 ms

alexis.jp screenshot

About Website

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

株式会社アレクシス-中国語、韓国語他、多言語の翻訳やDTP・WEB制作等を扱う東京都内の翻訳会社。また東京のホテルの情報サイト運営等、観光関連の情報発信に力を入れており、海外への情報発信など、ご相談・ご質問から丁寧にご対応させていただいております。

Visit alexis.jp

Key Findings

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

Performance Metrics

alexis.jp performance score

0

Network Requests Diagram

alexis.jp

743 ms

alexis.css

675 ms

jsapi

17 ms

googleanalytics.js

347 ms

analyze.js

837 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 64% of them (18 requests) were addressed to the original Alexis.jp, 11% (3 requests) were made to Junpei.analytics.qlook.net and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Mice-japan.alexis.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.7 kB (14%)

Content Size

166.2 kB

After Optimization

142.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-64%

Potential reduce by 6.6 kB

  • Original 10.3 kB
  • After minification 9.8 kB
  • After compression 3.7 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 6.6 kB or 64% of the original size.

Image Optimization

-4%

Potential reduce by 5.1 kB

  • Original 124.8 kB
  • After minification 119.7 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. Alexis images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 212 B

  • Original 17.6 kB
  • After minification 17.5 kB
  • After compression 17.4 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

-87%

Potential reduce by 11.8 kB

  • Original 13.5 kB
  • After minification 9.1 kB
  • After compression 1.7 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. Alexis.jp needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (12%)

Requests Now

26

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

alexis.jp

alexis.jp

743 ms

alexis.css

alexis.css

675 ms

jsapi

jsapi

17 ms

googleanalytics.js

googleanalytics.js

347 ms

analyze.js

analyze.js

837 ms

ga.js

ga.js

43 ms

ban_MICE-JAPAN.gif

ban_MICE-JAPAN.gif

874 ms

osaka_banner.jpg

osaka_banner.jpg

1301 ms

kyoto_banner.jpg

kyoto_banner.jpg

1309 ms

counter.png

counter.png

421 ms

alexis_logo-name.gif

alexis_logo-name.gif

360 ms

chinese_banner.gif

chinese_banner.gif

346 ms

korean_banner.gif

korean_banner.gif

337 ms

translation_banner.gif

translation_banner.gif

522 ms

inbound_banner.gif

inbound_banner.gif

704 ms

top_bunner_que.gif

top_bunner_que.gif

568 ms

top_bunner_yakkan.gif

top_bunner_yakkan.gif

506 ms

naru_bunner.gif

naru_bunner.gif

1077 ms

tensaku_bunner.gif

tensaku_bunner.gif

1079 ms

menu_org.jpg

menu_org.jpg

674 ms

erabikata_ban.gif

erabikata_ban.gif

868 ms

form_banner.gif

form_banner.gif

1134 ms

MIC-banner.gif

MIC-banner.gif

1025 ms

ban_tokyohotels.jpg

ban_tokyohotels.jpg

879 ms

2010EndlessDiscovery_169.gif

2010EndlessDiscovery_169.gif

1041 ms

__utm.gif

__utm.gif

12 ms

collect

collect

67 ms

analyze.png

analyze.png

445 ms

SEO Factors

alexis.jp SEO score

0

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

alexis.jp

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