Tools & Wizards About Us

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

plone.jp

Plone 5.2 : The Ultimate Enterprise CMS — Plone - エンタープライズ・オープンソースCMS　 Plone Users Group Japan

Page Load Speed

4.4 sec in total

First Response

670 ms

Resources Loaded

3.3 sec

Page Rendered

463 ms

About Website

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

最も完成されたオープンソースWebコンテンツ管理システム、Ploneの最新バージョン5.2がリリースされました。 Plone 5.2はPython3完全互換で、コア部分にREST APIを実装し、最新のZope4.0を取り込んでいます。

Visit plone.jp

Key Findings

We analyzed Plone.jp page load time and found that the first response time was 670 ms and then it took 3.8 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

plone.jp performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

plone.jp

670 ms

base-cachekey-1803e143edd8ae632ba174123cf540c1.css

359 ms

resourceplone.app.jquerytools.dateinput-cachekey-ec2f564083f79a9d12faeb723b468906.css

351 ms

resourceplonejp.content.content-cachekey-bdc6f2035a96260e30c5422098b87923.css

355 ms

themeplonejp.sthemestylesheetsmain-cachekey-bb4c0d5f4e63b31f71eb670c45ddad8b.css

366 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 38.5 kB (14%)

Content Size

278.6 kB

After Optimization

240.1 kB

  • HTML
  • Images

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

HTML Optimization

-67%

Potential reduce by 9.0 kB

  • Original 13.4 kB
  • After minification 11.8 kB
  • After compression 4.4 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.6 kB, which is 12% 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 9.0 kB or 67% of the original size.

Image Optimization

-11%

Potential reduce by 29.5 kB

  • Original 265.2 kB
  • After minification 235.8 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, Plone needs image optimization as it can save up to 29.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

plone.jp accessibility score

81

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.

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

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

plone.jp best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

plone.jp SEO score

96

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

    N/A

  • Encoding

    UTF-8

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

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