Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

1post.jp

理学療法士・作業療法士・言語聴覚士の求人、セミナー情報なら【POST】

Page Load Speed

10.9 sec in total

First Response

1.9 sec

Resources Loaded

8.8 sec

Page Rendered

252 ms

1post.jp screenshot

About Website

Click here to check amazing 1 POST content for Japan. Otherwise, check out these important facts you probably never knew about 1post.jp

POSTは理学療法士、作業療法士、言語聴覚士のためのリハビリ情報サイトです。求人・転職などの就職情報から、セミナー、勉強会、講習会などの学会情報、お役立ち情報などを発信しています。

Visit 1post.jp

Key Findings

We analyzed 1post.jp page load time and found that the first response time was 1.9 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

1post.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.27

45/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

1post.jp

1872 ms

style.css

357 ms

bootstrap.css

1326 ms

app.css

955 ms

advanced-responsive-video-embedder-public.css

361 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 40% of them (63 requests) were addressed to the original 1post.jp, 18% (28 requests) were made to O.twimg.com and 13% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain 1post.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (12%)

Content Size

12.7 MB

After Optimization

11.1 MB

In fact, the total size of 1post.jp main page is 12.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 45.6 kB

  • Original 58.9 kB
  • After minification 54.2 kB
  • After compression 13.3 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 45.6 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 730.8 kB

  • Original 11.6 MB
  • After minification 10.9 MB

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. 1 POST images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 346.1 kB

  • Original 477.0 kB
  • After minification 415.3 kB
  • After compression 130.8 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 346.1 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 458.0 kB

  • Original 540.6 kB
  • After minification 452.2 kB
  • After compression 82.6 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. 1post.jp needs all CSS files to be minified and compressed as it can save up to 458.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (47%)

Requests Now

154

After Optimization

82

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

Accessibility Review

1post.jp accessibility score

70

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

1post.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

1post.jp SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1post.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 1post.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

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