Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

yeah.but.jp

雛箱

Page Load Speed

3.5 sec in total

First Response

553 ms

Resources Loaded

2.8 sec

Page Rendered

142 ms

yeah.but.jp screenshot

About Website

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

Visit yeah.but.jp

Key Findings

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

Performance Metrics

yeah.but.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value1.2 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.7 s

100/100

10%

Network Requests Diagram

yeah.but.jp

553 ms

049001800

612 ms

back.gif

191 ms

Zen

383 ms

encount

558 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 29% of them (2 requests) were addressed to the original Yeah.but.jp, 29% (2 requests) were made to X4.mizubasyou.com and 29% (2 requests) were made to Asumi.shinobi.jp. The less responsive or slowest element that took the longest time to load (612 ms) relates to the external source X4.mizubasyou.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.7 kB (49%)

Content Size

5.5 kB

After Optimization

2.8 kB

In fact, the total size of Yeah.but.jp main page is 5.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 2.9 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 1.3 kB

  • Original 2.6 kB
  • After minification 2.4 kB
  • After compression 1.2 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 1.3 kB or 52% of the original size.

JavaScript Optimization

-47%

Potential reduce by 1.4 kB

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 1.6 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 1.4 kB or 47% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yeah But. According to our analytics all requests are already optimized.

Accessibility Review

yeah.but.jp accessibility score

89

Accessibility Issues

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

Best Practices

yeah.but.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

SEO Factors

yeah.but.jp SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

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