Tools & Wizards About Us
foge.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

foge.com

FO.video佛視頻 – AMTB.com淨宗同學網——CNOL.com中國在線佛陀教育

Page Load Speed

843 ms in total

First Response

157 ms

Resources Loaded

632 ms

Page Rendered

54 ms

foge.com screenshot

About Website

Visit foge.com now to see the best up-to-date FO Ge content and also check out these interesting facts you probably never knew about foge.com

眾神一體 宗教一家 平等對待 和睦相處 One Humanity, Many Faiths Treat All Equally and Live in Harmony 通過宗教教育和宗教合作參與實現世界和平與和諧 Achieving World Peace and Harmony through Religious Education and Engagement

Visit foge.com

Key Findings

We analyzed Foge.com page load time and found that the first response time was 157 ms and then it took 686 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

foge.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

foge.com

157 ms

ChinaOnline

131 ms

web-animations-next-lite.min.js

15 ms

webcomponents-all-noPatch.js

19 ms

fetch-polyfill.js

12 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Foge.com, 64% (14 requests) were made to Youtube.com and 18% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (157 ms) belongs to the original domain Foge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 652.6 kB (74%)

Content Size

885.3 kB

After Optimization

232.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Foge.com main page is 885.3 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. HTML takes 615.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 467.2 kB

  • Original 615.7 kB
  • After minification 615.7 kB
  • After compression 148.6 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 467.2 kB or 76% of the original size.

JavaScript Optimization

-68%

Potential reduce by 178.1 kB

  • Original 260.3 kB
  • After minification 259.3 kB
  • After compression 82.2 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 178.1 kB or 68% of the original size.

CSS Optimization

-79%

Potential reduce by 7.3 kB

  • Original 9.3 kB
  • After minification 9.3 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. Foge.com needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (86%)

Requests Now

14

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

foge.com

foge.com

157 ms

ChinaOnline

ChinaOnline

131 ms

web-animations-next-lite.min.js

web-animations-next-lite.min.js

15 ms

webcomponents-all-noPatch.js

webcomponents-all-noPatch.js

19 ms

fetch-polyfill.js

fetch-polyfill.js

12 ms

intersection-observer.min.js

intersection-observer.min.js

12 ms

scheduler.js

scheduler.js

5 ms

www-i18n-constants.js

www-i18n-constants.js

4 ms

www-tampering.js

www-tampering.js

4 ms

spf.js

spf.js

10 ms

network.js

network.js

9 ms

css2

css2

33 ms

www-onepick.css

www-onepick.css

8 ms

rs=AGKMywH8YSNgym6zCnJokUOi2m312kqt_Q

rs=AGKMywH8YSNgym6zCnJokUOi2m312kqt_Q

110 ms

desktop_polymer_legacy_browsers.js

desktop_polymer_legacy_browsers.js

41 ms

www-main-desktop-watch-page-skeleton.css

www-main-desktop-watch-page-skeleton.css

4 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

88 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

94 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

102 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

102 ms

InteractiveLogin

InteractiveLogin

33 ms

identifier

identifier

37 ms

Accessibility Review

foge.com accessibility score

81

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

foge.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

foge.com SEO score

99

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

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foge.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Foge.com main page’s claimed encoding is . 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

foge.com

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