Tools & Wizards About Us
pivot.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

pivot.jp

株式会社PIVOT | WEB・アプリ・システムのUI・UXデザイン企画・開発

Page Load Speed

2.9 sec in total

First Response

36 ms

Resources Loaded

1.9 sec

Page Rendered

909 ms

pivot.jp screenshot

About Website

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

株式会社PIVOTはデジタル領域のデザイン・開発を行う会社です。UXデザイン、UIデザイン、アプリ開発、システム開発までワンストップでご提供。真ん中に「人」がいるデジタルサービスで、心がおどる体験と、あたらしい発見をつくります。

Visit pivot.jp

Key Findings

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

Performance Metrics

pivot.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value66.6 s

0/100

25%

SI (Speed Index)

Value29.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value50.8 s

0/100

10%

Network Requests Diagram

pivot.jp

36 ms

pivot.jp

768 ms

ytag.js

1050 ms

style.css

22 ms

jquery-ui.min.css

31 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 84% of them (75 requests) were addressed to the original Pivot.jp, 3% (3 requests) were made to Contents.bownow.jp and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source S.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.7 kB (3%)

Content Size

9.9 MB

After Optimization

9.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pivot.jp main page is 9.9 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. Only a small number of websites need less resources to load. Images take 9.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 78.0 kB

  • Original 96.8 kB
  • After minification 79.4 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 17.4 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.0 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 177.8 kB

  • Original 9.6 MB
  • After minification 9.5 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. Pivot images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.8 kB

  • Original 168.2 kB
  • After minification 168.2 kB
  • After compression 166.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

-0%

Potential reduce by 119 B

  • Original 27.9 kB
  • After minification 27.9 kB
  • After compression 27.8 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. Pivot.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (43%)

Requests Now

87

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pivot.jp

pivot.jp

36 ms

pivot.jp

pivot.jp

768 ms

ytag.js

ytag.js

1050 ms

style.css

style.css

22 ms

jquery-ui.min.css

jquery-ui.min.css

31 ms

home.css

home.css

30 ms

column.css

column.css

32 ms

slick.min.css

slick.min.css

34 ms

js

js

109 ms

sdk.js

sdk.js

53 ms

widgets.js

widgets.js

52 ms

gtm.js

gtm.js

76 ms

lak6hxq.js

lak6hxq.js

166 ms

trace.js

trace.js

839 ms

logo-large.png

logo-large.png

28 ms

logo-small.png

logo-small.png

28 ms

logo.svg

logo.svg

27 ms

home_top_1.jpg

home_top_1.jpg

28 ms

home_top_1_sp.jpg

home_top_1_sp.jpg

28 ms

home_top_2.jpg

home_top_2.jpg

60 ms

home_top_2_sp.jpg

home_top_2_sp.jpg

59 ms

1.png

1.png

67 ms

ic_arrow_right.svg

ic_arrow_right.svg

28 ms

1.jpg

1.jpg

61 ms

1.jpg

1.jpg

68 ms

1.jpg

1.jpg

120 ms

1.png

1.png

122 ms

1.jpg

1.jpg

118 ms

1.jpg

1.jpg

131 ms

1.jpg

1.jpg

128 ms

home_slogan_sp.svg

home_slogan_sp.svg

126 ms

ic_pivot_flag_hover.png

ic_pivot_flag_hover.png

124 ms

ic_pivot_flag_up.png

ic_pivot_flag_up.png

124 ms

ic_pivot_flag_down.png

ic_pivot_flag_down.png

129 ms

sdk.js

sdk.js

21 ms

575 ms

home_planning_1.jpg

home_planning_1.jpg

11 ms

ic_flash.svg

ic_flash.svg

10 ms

home_planning_3.jpg

home_planning_3.jpg

16 ms

ic_file_check.svg

ic_file_check.svg

13 ms

home_planning_2.jpg

home_planning_2.jpg

14 ms

ic_file_heart.svg

ic_file_heart.svg

11 ms

home_planning_4.jpg

home_planning_4.jpg

71 ms

ic_haft_gear.svg

ic_haft_gear.svg

83 ms

home_planning_5.jpg

home_planning_5.jpg

72 ms

ic_design_1.svg

ic_design_1.svg

77 ms

home_planning_6.jpg

home_planning_6.jpg

75 ms

ic_design_2.svg

ic_design_2.svg

78 ms

home_planning_7.jpg

home_planning_7.jpg

76 ms

ic_design_3.svg

ic_design_3.svg

80 ms

home_planning_8.jpg

home_planning_8.jpg

88 ms

ic_design_4.svg

ic_design_4.svg

86 ms

service_dev_1.jpg

service_dev_1.jpg

122 ms

ic_code.svg

ic_code.svg

85 ms

service_dev_2.jpg

service_dev_2.jpg

87 ms

ic_git.svg

ic_git.svg

83 ms

service_dev_3.jpg

service_dev_3.jpg

88 ms

ic_gear.svg

ic_gear.svg

89 ms

service_improve_1.jpg

service_improve_1.jpg

90 ms

ic_improve_1.svg

ic_improve_1.svg

90 ms

1.png

1.png

122 ms

1.jpg

1.jpg

100 ms

logo.svg

logo.svg

92 ms

home_pivot.jpg

home_pivot.jpg

93 ms

home_pivot_sp.jpg

home_pivot_sp.jpg

91 ms

ic_arrow.svg

ic_arrow.svg

96 ms

ic_map.svg

ic_map.svg

95 ms

icon-contact-1.png

icon-contact-1.png

98 ms

icon-contact-2.png

icon-contact-2.png

114 ms

jquery.min.js

jquery.min.js

98 ms

jquery-ui.min.js

jquery-ui.min.js

116 ms

jquery.bez.min.js

jquery.bez.min.js

111 ms

header.js

header.js

110 ms

scrollax.min.js

scrollax.min.js

111 ms

curtains.umd.min.js

curtains.umd.min.js

111 ms

logo-animation.js

logo-animation.js

115 ms

slick.min.js

slick.min.js

113 ms

p.gif

p.gif

420 ms

moment.min.js

moment.min.js

230 ms

jquery.collapser.min.js

jquery.collapser.min.js

227 ms

slider.js

slider.js

224 ms

tab.js

tab.js

222 ms

news.js

news.js

222 ms

home.js

home.js

218 ms

column.js

column.js

220 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

39 ms

settings

settings

75 ms

trace.js

trace.js

169 ms

trace.js

trace.js

264 ms

Accessibility Review

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

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

pivot.jp best practices score

83

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

Page has valid source maps

SEO Factors

pivot.jp SEO score

99

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 Pivot.jp 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 Pivot.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

pivot.jp

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