Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

cumis.com

Credit union protection, insurance and financial solutions – CUMIS

Page Load Speed

1.6 sec in total

First Response

395 ms

Resources Loaded

1.2 sec

Page Rendered

53 ms

cumis.com screenshot

About Website

Visit cumis.com now to see the best up-to-date CUMIS content for Canada and also check out these interesting facts you probably never knew about cumis.com

CUMIS provides exclusive personal and business insurance solutions, and financial services to Canada’s credit unions and their members.

Visit cumis.com

Key Findings

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

Performance Metrics

cumis.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

cumis

395 ms

gtm.js

70 ms

bootstrap-grid.min.css

57 ms

remixicon.css

95 ms

css2

53 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Cumis.com, 17% (7 requests) were made to and 15% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source Www-cumis.cooperators.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 282.7 kB (44%)

Content Size

645.5 kB

After Optimization

362.9 kB

In fact, the total size of Cumis.com main page is 645.5 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. 65% of websites need less resources to load. CSS take 349.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 31.4 kB

  • Original 36.8 kB
  • After minification 23.9 kB
  • After compression 5.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 13.0 kB, which is 35% 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 31.4 kB or 85% of the original size.

JavaScript Optimization

-62%

Potential reduce by 162.0 kB

  • Original 259.7 kB
  • After minification 259.7 kB
  • After compression 97.7 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 162.0 kB or 62% of the original size.

CSS Optimization

-26%

Potential reduce by 89.3 kB

  • Original 349.0 kB
  • After minification 349.0 kB
  • After compression 259.7 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. Cumis.com needs all CSS files to be minified and compressed as it can save up to 89.3 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (59%)

Requests Now

27

After Optimization

11

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

Accessibility Review

cumis.com accessibility score

100

Accessibility Issues

Best Practices

cumis.com best practices score

92

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

SEO Factors

cumis.com SEO score

93

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

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cumis.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Cumis.com 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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: