Tools & Wizards About Us
ocist.org screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

ocist.org

Ordo Cistercensis - Ordo Cistercensis

Page Load Speed

4.9 sec in total

First Response

374 ms

Resources Loaded

4.4 sec

Page Rendered

217 ms

ocist.org screenshot

About Website

Welcome to ocist.org homepage info - get ready to check Ocist best content for Italy right away, or after learning these important things about ocist.org

Ordo Cistercensis, Benevenuti nelle pagine dell'Ordine Cistercensis.

Visit ocist.org

Key Findings

We analyzed Ocist.org page load time and found that the first response time was 374 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ocist.org performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

ocist.org

374 ms

www.ocist.org

341 ms

442 ms

template.css

144 ms

jquery.min.js

398 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 84% of them (64 requests) were addressed to the original Ocist.org, 9% (7 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Ocist.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ocist.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.5 kB (8%)

Content Size

2.4 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ocist.org main page is 2.4 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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 75.2 kB

  • Original 90.2 kB
  • After minification 84.5 kB
  • After compression 15.0 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 75.2 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 87.9 kB

  • Original 2.0 MB
  • After minification 1.9 MB

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. Ocist images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 17.0 kB

  • Original 253.8 kB
  • After minification 253.8 kB
  • After compression 236.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 7.5 kB

  • Original 75.6 kB
  • After minification 75.5 kB
  • After compression 68.1 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. Ocist.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (72%)

Requests Now

65

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ocist. 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 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ocist.org

ocist.org

374 ms

www.ocist.org

www.ocist.org

341 ms

442 ms

template.css

template.css

144 ms

jquery.min.js

jquery.min.js

398 ms

jquery-noconflict.js

jquery-noconflict.js

370 ms

jquery-migrate.min.js

jquery-migrate.min.js

355 ms

caption.js

caption.js

370 ms

bootstrap.min.js

bootstrap.min.js

373 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

379 ms

jquery.ui.sortable.min.js

jquery.ui.sortable.min.js

482 ms

jquery-ui-addons.js

jquery-ui-addons.js

631 ms

mootools-core.js

mootools-core.js

625 ms

core.js

core.js

521 ms

mootools-more.js

mootools-more.js

766 ms

jquery.colorbox.js

jquery.colorbox.js

537 ms

s5box.css

s5box.css

607 ms

jd.gallery.jquery.js

jd.gallery.jquery.js

653 ms

jd.gallery.transitions.jquery.js

jd.gallery.transitions.jquery.js

667 ms

bootstrap-default-min.css

bootstrap-default-min.css

850 ms

bootstrap-responsive.css

bootstrap-responsive.css

756 ms

font-awesome.min.css

font-awesome.min.css

791 ms

ionicons.min.css

ionicons.min.css

792 ms

css

css

38 ms

s5_flex_menu-min.js

s5_flex_menu-min.js

802 ms

s5_flex_menu.css

s5_flex_menu.css

910 ms

system.css

system.css

926 ms

general.css

general.css

921 ms

template_default.css

template_default.css

928 ms

template.css

template.css

933 ms

com_content.css

com_content.css

974 ms

editor.css

editor.css

1047 ms

thirdparty.css

thirdparty.css

1071 ms

css

css

56 ms

multibox.css

multibox.css

1069 ms

ajax.css

ajax.css

1067 ms

overlay.js

overlay.js

1062 ms

multibox.js

multibox.js

1099 ms

s5_font_adjuster-min.js

s5_font_adjuster-min.js

1173 ms

s5_responsive_bars-min.css

s5_responsive_bars-min.css

1195 ms

s5_responsive_hide_classes-min.css

s5_responsive_hide_classes-min.css

1213 ms

s5_responsive.css

s5_responsive.css

1088 ms

s5_info_slide-min.css

s5_info_slide-min.css

875 ms

s5imagecontent.css

s5imagecontent.css

875 ms

s5_info_slide-min.js

s5_info_slide-min.js

1158 ms

scrollReveal-min.js

scrollReveal-min.js

960 ms

s5_responsive_mobile_bar-min.js

s5_responsive_mobile_bar-min.js

1164 ms

iCarousel_jquery.js

iCarousel_jquery.js

1132 ms

s5_activejs.js

s5_activejs.js

1069 ms

s5_box_hide_div.js

s5_box_hide_div.js

851 ms

system.css

system.css

533 ms

top1.jpg

top1.jpg

962 ms

top2.jpg

top2.jpg

848 ms

top3.jpg

top3.jpg

963 ms

search_light.png

search_light.png

135 ms

arrow_light.png

arrow_light.png

137 ms

menu_light.png

menu_light.png

134 ms

s5_logo.png

s5_logo.png

256 ms

iacf3.jpg

iacf3.jpg

574 ms

iacf2.jpg

iacf2.jpg

1134 ms

iacf1.jpg

iacf1.jpg

721 ms

pp1.jpg

pp1.jpg

280 ms

4UacrEBBsBhlBjvfkQjt71kZfyBzPgNG9hU4-6qm.ttf

4UacrEBBsBhlBjvfkQjt71kZfyBzPgNG9hU4-6qm.ttf

35 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

32 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

33 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

32 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

33 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

30 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

30 ms

styles.css

styles.css

223 ms

row_bg.jpg

row_bg.jpg

622 ms

ionicons.ttf

ionicons.ttf

608 ms

s5_scroll_arrow.png

s5_scroll_arrow.png

161 ms

border1.png

border1.png

242 ms

border2.png

border2.png

405 ms

s5_menu_arrow.png

s5_menu_arrow.png

406 ms

Accessibility Review

ocist.org accessibility score

78

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.

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

Form elements do not have associated labels

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

ocist.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ocist.org SEO score

81

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

ocist.org

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