Tools & Wizards About Us
stplanning.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

stplanning.jp

株式会社 エス・ティー・プランニング | 宮崎市南花ヶ島町

Page Load Speed

3.1 sec in total

First Response

544 ms

Resources Loaded

2.4 sec

Page Rendered

108 ms

stplanning.jp screenshot

About Website

Click here to check amazing Stplanning content. Otherwise, check out these important facts you probably never knew about stplanning.jp

株式会社 エス・ティー・プランニング | 宮崎市南花ヶ島町 株式会社 エス・ティー・プランニングは目的にあった広告展開を提案し販売促進のお手伝いをいたします。私たちについて. プレゼン / コンサル事業. サイン事業. 販促ツール事業. 採用情報. お問い合わせ.

Visit stplanning.jp

Key Findings

We analyzed Stplanning.jp page load time and found that the first response time was 544 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

stplanning.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

stplanning.jp

544 ms

hpbparts.css

341 ms

container_1Md_2c_right.css

350 ms

main_1Md_2c3.css

352 ms

user.css

378 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that all of those requests were addressed to Stplanning.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Stplanning.jp.

Page Optimization Overview & Recommendations

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

Content Size

535.7 kB

After Optimization

412.7 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Stplanning.jp main page is 535.7 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. Images take 486.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 3.9 kB

  • Original 5.7 kB
  • After minification 4.6 kB
  • After compression 1.8 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 1.0 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 3.9 kB or 69% of the original size.

Image Optimization

-16%

Potential reduce by 80.0 kB

  • Original 486.6 kB
  • After minification 406.6 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. Obviously, Stplanning needs image optimization as it can save up to 80.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-90%

Potential reduce by 39.1 kB

  • Original 43.5 kB
  • After minification 25.4 kB
  • After compression 4.4 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. Stplanning.jp needs all CSS files to be minified and compressed as it can save up to 39.1 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (53%)

Requests Now

17

After Optimization

8

  • Images
  • CSS

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

Network Requests Diagram

stplanning.jp

stplanning.jp

544 ms

hpbparts.css

hpbparts.css

341 ms

container_1Md_2c_right.css

container_1Md_2c_right.css

350 ms

main_1Md_2c3.css

main_1Md_2c3.css

352 ms

user.css

user.css

378 ms

pageBg_1Md_01.png

pageBg_1Md_01.png

319 ms

footerBg_1Md.png

footerBg_1Md.png

329 ms

logo_1Md4.png

logo_1Md4.png

342 ms

top_mainimg_1Md_01.png

top_mainimg_1Md_01.png

1509 ms

indexBg_1Md_01.png

indexBg_1Md_01.png

344 ms

point_1Md.png

point_1Md.png

342 ms

returnTop_1Md.png

returnTop_1Md.png

661 ms

mainmenu_1Md_01.png

mainmenu_1Md_01.png

663 ms

banner_1Md_01.png

banner_1Md_01.png

803 ms

banner_1Md_02.png

banner_1Md_02.png

872 ms

banner_1Md_03.png

banner_1Md_03.png

877 ms

companyBg_1Md.png

companyBg_1Md.png

991 ms

fPoint_1Md.png

fPoint_1Md.png

995 ms

Accessibility Review

stplanning.jp accessibility score

69

Accessibility Issues

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

stplanning.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

stplanning.jp SEO score

91

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stplanning.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 Stplanning.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

stplanning.jp

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