Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

zayray.com

Uターン転職の良いところ悪いところ

Page Load Speed

6.7 sec in total

First Response

723 ms

Resources Loaded

5.8 sec

Page Rendered

135 ms

About Website

Visit zayray.com now to see the best up-to-date Zayray content and also check out these interesting facts you probably never knew about zayray.com

Uターン転職とは、一度都市部に出て就職をした後、地元に戻って転職することである。地元に貢献したい、親を安心させたいなど若い人にもUターン転職者が増えているが、収入面や生活の利便性といったデメリットを考える必要があるだろう。

Visit zayray.com

Key Findings

We analyzed Zayray.com page load time and found that the first response time was 723 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

zayray.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

zayray.com

723 ms

www.zayray.com

4189 ms

style.min.css

1022 ms

css

24 ms

style.css

771 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 67% of them (6 requests) were addressed to the original Zayray.com, 22% (2 requests) were made to Fonts.gstatic.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Zayray.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.9 kB (74%)

Content Size

206.3 kB

After Optimization

53.3 kB

In fact, the total size of Zayray.com main page is 206.3 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. Only 10% of websites need less resources to load. CSS take 148.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 21.4 kB

  • Original 29.6 kB
  • After minification 29.3 kB
  • After compression 8.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 21.4 kB or 72% of the original size.

Image Optimization

-8%

Potential reduce by 2.2 kB

  • Original 25.4 kB
  • After minification 23.3 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. Zayray images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 1.6 kB

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 1.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 1.6 kB or 55% of the original size.

CSS Optimization

-86%

Potential reduce by 127.8 kB

  • Original 148.3 kB
  • After minification 140.8 kB
  • After compression 20.5 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. Zayray.com needs all CSS files to be minified and compressed as it can save up to 127.8 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zayray. According to our analytics all requests are already optimized.

Accessibility Review

zayray.com accessibility score

91

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

zayray.com 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

SEO Factors

zayray.com SEO score

95

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

High

Tap targets are not sized appropriately

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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: