Tools & Wizards About Us
support.iocc.org screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

support.iocc.org

Worldwide Relief | International Orthodox Christian Charities

Page Load Speed

1.5 sec in total

First Response

44 ms

Resources Loaded

1.4 sec

Page Rendered

49 ms

support.iocc.org screenshot

About Website

Welcome to support.iocc.org homepage info - get ready to check Support Iocc best content for United States right away, or after learning these important things about support.iocc.org

International Orthodox Christian Charities offers worldwide emergency relief & development programs to those in need worldwide, without discrimination.

Visit support.iocc.org

Key Findings

We analyzed Support.iocc.org page load time and found that the first response time was 44 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

support.iocc.org performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value3,020 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.393

26/100

15%

TTI (Time to Interactive)

Value31.7 s

0/100

10%

Network Requests Diagram

support.iocc.org

44 ms

621 ms

main.css

102 ms

ddplugin.css

50 ms

airgap.js

85 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Support.iocc.org, 24% (5 requests) were made to Prod-frs.content.classy.org and 10% (2 requests) were made to Give.iocc.org. The less responsive or slowest element that took the longest time to load (621 ms) relates to the external source Give.iocc.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.6 kB (6%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Support.iocc.org main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 80.4 kB

  • Original 113.1 kB
  • After minification 111.6 kB
  • After compression 32.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 80.4 kB or 71% of the original size.

JavaScript Optimization

-0%

Potential reduce by 207 B

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 146.5 kB
  • After minification 146.5 kB
  • After compression 146.5 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. Support.iocc.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (83%)

Requests Now

18

After Optimization

3

  • JavaScript
  • CSS

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

Network Requests Diagram

support.iocc.org

support.iocc.org

44 ms

621 ms

main.css

main.css

102 ms

ddplugin.css

ddplugin.css

50 ms

airgap.js

airgap.js

85 ms

js

js

83 ms

54 ms

20864580600.js

20864580600.js

59 ms

link-initialize.js

link-initialize.js

79 ms

libs.min.js

libs.min.js

163 ms

module.min.js

module.min.js

187 ms

module.min.js

module.min.js

180 ms

paypal-js.legacy.min.js

paypal-js.legacy.min.js

62 ms

iframe-v3.min.js

iframe-v3.min.js

196 ms

rocket-loader.min.js

rocket-loader.min.js

21 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

76 ms

fontello.css

fontello.css

14 ms

js

js

72 ms

7 ms

20864580600.js

20864580600.js

26 ms

libs.min.js

libs.min.js

31 ms

Accessibility Review

support.iocc.org accessibility score

92

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Best Practices

support.iocc.org 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

support.iocc.org SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.iocc.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Support.iocc.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

support.iocc.org

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