Tools & Wizards About Us
point-house.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

point-house.jp

- Ｐ・Ｈ

Page Load Speed

5 sec in total

First Response

939 ms

Resources Loaded

3.7 sec

Page Rendered

389 ms

point-house.jp screenshot

About Website

Welcome to point-house.jp homepage info - get ready to check Point House best content for Japan right away, or after learning these important things about point-house.jp

P・H（ピーエイチ）は恋する女子の未来を応援するWEBメディアです。最新コスメやメイクなどのビューティ情報からSNSのトレンドやエンタメ情報まで、あなたの明日が今よりもほんの少し良くなるための情報を発信しています。

Visit point-house.jp

Key Findings

We analyzed Point-house.jp page load time and found that the first response time was 939 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

point-house.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

point-house.jp

939 ms

js

102 ms

wp-emoji-release.min.js

205 ms

style.min.css

349 ms

wpp.css

400 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 80% of them (49 requests) were addressed to the original Point-house.jp, 5% (3 requests) were made to Googleads.g.doubleclick.net and 3% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Point-house.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.4 kB (17%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 42.4 kB

  • Original 53.5 kB
  • After minification 48.4 kB
  • After compression 11.1 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 42.4 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 50.8 kB

  • Original 637.2 kB
  • After minification 586.4 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. Point House images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 101.9 kB

  • Original 493.9 kB
  • After minification 493.8 kB
  • After compression 391.9 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 101.9 kB or 21% of the original size.

CSS Optimization

-34%

Potential reduce by 17.4 kB

  • Original 50.5 kB
  • After minification 50.1 kB
  • After compression 33.1 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. Point-house.jp needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (44%)

Requests Now

59

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

point-house.jp

point-house.jp

939 ms

js

js

102 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

205 ms

style.min.css

style.min.css

349 ms

wpp.css

wpp.css

400 ms

style.css

style.css

602 ms

style.css

style.css

397 ms

css

css

51 ms

normalize.css

normalize.css

399 ms

font-awesome.min.css

font-awesome.min.css

400 ms

st-kanricss.php

st-kanricss.php

553 ms

st-rankcss.php

st-rankcss.php

625 ms

st-themecss-loader.php

st-themecss-loader.php

663 ms

wpp-5.0.0.min.js

wpp-5.0.0.min.js

606 ms

jquery.min.js

jquery.min.js

22 ms

adsbygoogle.js

adsbygoogle.js

140 ms

common.css

common.css

606 ms

jquery.bxslider.css

jquery.bxslider.css

745 ms

jquery-3.3.1.js

jquery-3.3.1.js

1169 ms

jquery.bxslider.js

jquery.bxslider.js

979 ms

script.js

script.js

788 ms

udatareru.js

udatareru.js

817 ms

base.js

base.js

855 ms

scroll.js

scroll.js

889 ms

jquery.tubular.1.0.js

jquery.tubular.1.0.js

982 ms

wp-embed.min.js

wp-embed.min.js

1047 ms

show_ads_impl.js

show_ads_impl.js

259 ms

logo.png

logo.png

211 ms

search.png

search.png

508 ms

101-53.jpg

101-53.jpg

1020 ms

101-21.jpg

101-21.jpg

855 ms

101-52.jpg

101-52.jpg

992 ms

101-30.jpg

101-30.jpg

1189 ms

101-33.jpg

101-33.jpg

1186 ms

p2504.jpg

p2504.jpg

1189 ms

1-2-400x300.jpeg

1-2-400x300.jpeg

1029 ms

1-1-400x300.jpeg

1-1-400x300.jpeg

1188 ms

1-400x300.jpeg

1-400x300.jpeg

1197 ms

1-4-400x300.jpeg

1-4-400x300.jpeg

1197 ms

1-3-400x300.jpeg

1-3-400x300.jpeg

1380 ms

1-2-400x300.jpeg

1-2-400x300.jpeg

1381 ms

1-1-400x300.jpeg

1-1-400x300.jpeg

1382 ms

1-400x300.jpeg

1-400x300.jpeg

1382 ms

1-4-400x300.jpeg

1-4-400x300.jpeg

1358 ms

1-3-400x300.jpeg

1-3-400x300.jpeg

1367 ms

1-2-400x300.jpeg

1-2-400x300.jpeg

1527 ms

1-1-400x300.jpeg

1-1-400x300.jpeg

1537 ms

bnr_lifechannel.png

bnr_lifechannel.png

208 ms

lifeComics_logo.png

lifeComics_logo.png

208 ms

pagetop_pc.png

pagetop_pc.png

208 ms

pagetop_sp.png

pagetop_sp.png

208 ms

logo_footer.png

logo_footer.png

409 ms

api.ipify.org

api.ipify.org

105 ms

next.png

next.png

355 ms

zrt_lookup.html

zrt_lookup.html

97 ms

ads

ads

412 ms

visitcompany

visitcompany

65 ms

ads

ads

380 ms

prev.png

prev.png

236 ms

iframe_api

iframe_api

45 ms

www-widgetapi.js

www-widgetapi.js

4 ms

Accessibility Review

point-house.jp accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

point-house.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

Page has valid source maps

SEO Factors

point-house.jp SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Point-house.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 Point-house.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

point-house.jp

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