Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

yoppa.org

yoppa org

Page Load Speed

5.6 sec in total

First Response

1.7 sec

Resources Loaded

3.6 sec

Page Rendered

265 ms

yoppa.org screenshot

About Website

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

田所淳のWebページ。大学の講義などの資料を掲載しています。openFrameworks、Processing、Arduino、Pure Data、Max/MSP、HTML5の情報など。

Visit yoppa.org

Key Findings

We analyzed Yoppa.org page load time and found that the first response time was 1.7 sec and then it took 3.9 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

yoppa.org performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

yoppa.org

1731 ms

style.css

622 ms

style-ia3-1.0.2.css

330 ms

style-fancybox-1.3.1.css

664 ms

modernizr-1.5.min.js

499 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 37% of them (19 requests) were addressed to the original Yoppa.org, 8% (4 requests) were made to Platform.twitter.com and 6% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Yoppa.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.2 kB (48%)

Content Size

434.5 kB

After Optimization

226.3 kB

In fact, the total size of Yoppa.org main page is 434.5 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. 40% of websites need less resources to load. CSS take 154.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 30.3 kB

  • Original 43.0 kB
  • After minification 39.7 kB
  • After compression 12.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. 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 30.3 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 6 B

  • Original 98.1 kB
  • After minification 98.1 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. Yoppa images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 65.7 kB

  • Original 139.2 kB
  • After minification 136.5 kB
  • After compression 73.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 65.7 kB or 47% of the original size.

CSS Optimization

-73%

Potential reduce by 112.2 kB

  • Original 154.3 kB
  • After minification 150.3 kB
  • After compression 42.0 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. Yoppa.org needs all CSS files to be minified and compressed as it can save up to 112.2 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (66%)

Requests Now

50

After Optimization

17

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

Accessibility Review

yoppa.org accessibility score

77

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

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

yoppa.org 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yoppa.org SEO score

87

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 Yoppa.org 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 Yoppa.org 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

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