Tools & Wizards About Us
fgpe.net screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fgpe.net

地球環境平和財団 Official Site

Page Load Speed

5.1 sec in total

First Response

1.2 sec

Resources Loaded

3.8 sec

Page Rendered

136 ms

fgpe.net screenshot

About Website

Welcome to fgpe.net homepage info - get ready to check Fgpe best content right away, or after learning these important things about fgpe.net

地球環境保全と世界平和をテーマに1991 年から活動を開始。国連環境計画（UNEP）との共催で「子供環境ポスター原画コンテスト」や「子供環境会議」、「地球環境米米フォーラム」、「地球の森プロジェクト」、「地球環境テニスフォーラム」などのユニークな活動を、国際機関や各国政府、地方自治体、企業、団体とのコラボレーションで国際的に展開してきました。

Visit fgpe.net

Key Findings

We analyzed Fgpe.net page load time and found that the first response time was 1.2 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 65% of websites can load faster.

Performance Metrics

fgpe.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

fgpe.net

1197 ms

style.css

496 ms

xfade2.js

355 ms

jquery-1.6.1.min.js

1083 ms

sagscroller.js

546 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that all of those requests were addressed to Fgpe.net 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 Fgpe.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.5 kB (13%)

Content Size

663.8 kB

After Optimization

577.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fgpe.net main page is 663.8 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. 20% of websites need less resources to load. Images take 542.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 6.2 kB

  • Original 8.5 kB
  • After minification 8.3 kB
  • After compression 2.3 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 6.2 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 4.2 kB

  • Original 542.2 kB
  • After minification 538.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. Fgpe images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 67.8 kB

  • Original 102.7 kB
  • After minification 99.5 kB
  • After compression 34.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 67.8 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 8.3 kB

  • Original 10.3 kB
  • After minification 8.2 kB
  • After compression 2.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. Fgpe.net needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

23

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fgpe.net

fgpe.net

1197 ms

style.css

style.css

496 ms

xfade2.js

xfade2.js

355 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

1083 ms

sagscroller.js

sagscroller.js

546 ms

ajaxloading.gif

ajaxloading.gif

807 ms

slide0.jpg

slide0.jpg

543 ms

slide1.jpg

slide1.jpg

497 ms

slide2.jpg

slide2.jpg

924 ms

contents_back.png

contents_back.png

184 ms

logo.gif

logo.gif

546 ms

nav_back.jpg

nav_back.jpg

366 ms

nav_action.png

nav_action.png

548 ms

nav_about.png

nav_about.png

662 ms

top_upinfo_list_back.gif

top_upinfo_list_back.gif

723 ms

05-150x150.jpg

05-150x150.jpg

909 ms

%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1-150x150.gif

%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A-1-150x150.gif

730 ms

01-150x150.jpg

01-150x150.jpg

827 ms

P1000153-150x150.jpg

P1000153-150x150.jpg

903 ms

P1000148-c-150x150.jpg

P1000148-c-150x150.jpg

912 ms

15-150x150.jpg

15-150x150.jpg

1140 ms

no_image.jpg

no_image.jpg

1157 ms

01-150x150.jpg

01-150x150.jpg

1082 ms

1st-150x150.jpg

1st-150x150.jpg

1089 ms

footer_logo.gif

footer_logo.gif

1093 ms

xfade2.css

xfade2.css

521 ms

Accessibility Review

fgpe.net accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fgpe.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fgpe.net SEO score

90

Search Engine Optimization Advices

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 Fgpe.net 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 Fgpe.net 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

fgpe.net

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