Tools & Wizards About Us
strikepro.jp screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

strikepro.jp

STRIKE｜ストライクプロダクション

Page Load Speed

4.1 sec in total

First Response

884 ms

Resources Loaded

3 sec

Page Rendered

196 ms

strikepro.jp screenshot

About Website

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

恵比寿にあるモデル・タレントプロダクション

Visit strikepro.jp

Key Findings

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

Performance Metrics

strikepro.jp performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

strikepro.jp

884 ms

normalize.css

334 ms

cf.css

334 ms

bace.css

345 ms

common.css

368 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 91% of them (43 requests) were addressed to the original Strikepro.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Strikepro.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.2 kB (23%)

Content Size

723.9 kB

After Optimization

560.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Strikepro.jp main page is 723.9 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. 25% of websites need less resources to load. Images take 409.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.4 kB

  • Original 20.1 kB
  • After minification 14.4 kB
  • After compression 4.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 5.7 kB, which is 28% 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 15.4 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 3.5 kB

  • Original 409.8 kB
  • After minification 406.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. STRIKE Pro images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 124.8 kB

  • Original 270.6 kB
  • After minification 237.1 kB
  • After compression 145.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 124.8 kB or 46% of the original size.

CSS Optimization

-83%

Potential reduce by 19.5 kB

  • Original 23.4 kB
  • After minification 12.6 kB
  • After compression 3.9 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. Strikepro.jp needs all CSS files to be minified and compressed as it can save up to 19.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (60%)

Requests Now

45

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STRIKE Pro. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

strikepro.jp

strikepro.jp

884 ms

normalize.css

normalize.css

334 ms

cf.css

cf.css

334 ms

bace.css

bace.css

345 ms

common.css

common.css

368 ms

index2.css

index2.css

368 ms

jquery.bxslider.css

jquery.bxslider.css

369 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1160 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

499 ms

menu.js

menu.js

517 ms

jquery.bxslider.js

jquery.bxslider.js

916 ms

smoothAnchor.js

smoothAnchor.js

551 ms

js

js

51 ms

google_map_min.js

google_map_min.js

554 ms

navi.js

navi.js

664 ms

footer.js

footer.js

509 ms

analytics.js

analytics.js

21 ms

strike_logo.png

strike_logo.png

186 ms

bt_sns_fb.png

bt_sns_fb.png

185 ms

top_ico_mail.gif

top_ico_mail.gif

186 ms

top_ico_tel.gif

top_ico_tel.gif

173 ms

main_img_06.jpg

main_img_06.jpg

997 ms

main_img_07.jpg

main_img_07.jpg

664 ms

index_h2_news.gif

index_h2_news.gif

347 ms

index_h2_blog.gif

index_h2_blog.gif

369 ms

index_h2_talent.gif

index_h2_talent.gif

370 ms

index_oono_misaki.jpg

index_oono_misaki.jpg

555 ms

index_abe_cocoha.jpg

index_abe_cocoha.jpg

689 ms

nav_home_d.png

nav_home_d.png

536 ms

nav_talent_d.png

nav_talent_d.png

540 ms

nav_recruit_d.png

nav_recruit_d.png

721 ms

nav_company_d.png

nav_company_d.png

726 ms

nav_contact_d.png

nav_contact_d.png

725 ms

under_line.gif

under_line.gif

814 ms

icon_brank.gif

icon_brank.gif

847 ms

collect

collect

43 ms

bt_top.gif

bt_top.gif

842 ms

footer_logo.png

footer_logo.png

848 ms

nav_home_d_on.png

nav_home_d_on.png

849 ms

nav_home_d_on_on.png

nav_home_d_on_on.png

918 ms

nav_talent_d_on.png

nav_talent_d_on.png

957 ms

nav_recruit_d_on.png

nav_recruit_d_on.png

1025 ms

nav_company_d_on.png

nav_company_d_on.png

1033 ms

nav_contact_d_on.png

nav_contact_d_on.png

1034 ms

bx_loader.gif

bx_loader.gif

1084 ms

controls.png

controls.png

1084 ms

js

js

67 ms

Accessibility Review

strikepro.jp accessibility score

77

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.

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

strikepro.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

strikepro.jp SEO score

89

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

    JA

  • Encoding

    UTF-8

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

strikepro.jp

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