Tools & Wizards About Us
colloquy.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

colloquy.com

Partners in rewarding Canadians | Work with AIR MILES

Page Load Speed

1.8 sec in total

First Response

245 ms

Resources Loaded

1.3 sec

Page Rendered

285 ms

colloquy.com screenshot

About Website

Visit colloquy.com now to see the best up-to-date Colloquy content for United States and also check out these interesting facts you probably never knew about colloquy.com

We help businesses strengthen customer relationships and develop opportunities to build new ones through the capabilities of Canada’s most recognized loyalty program.

Visit colloquy.com

Key Findings

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

Performance Metrics

colloquy.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

colloquy.com

245 ms

main.min.css

361 ms

jquery.min.js

67 ms

iMAWebCookie.js

110 ms

combined.min.js

238 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 71% of them (30 requests) were addressed to the original Colloquy.com, 7% (3 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (361 ms) belongs to the original domain Colloquy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.2 kB (16%)

Content Size

555.7 kB

After Optimization

468.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Colloquy.com main page is 555.7 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. 40% of websites need less resources to load. Images take 441.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 67.3 kB

  • Original 78.7 kB
  • After minification 61.6 kB
  • After compression 11.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 17.1 kB, which is 22% 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 67.3 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 10.8 kB

  • Original 441.9 kB
  • After minification 431.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. Colloquy images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 9.1 kB

  • Original 35.2 kB
  • After minification 34.9 kB
  • After compression 26.1 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 9.1 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (22%)

Requests Now

36

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

colloquy.com

colloquy.com

245 ms

main.min.css

main.min.css

361 ms

jquery.min.js

jquery.min.js

67 ms

iMAWebCookie.js

iMAWebCookie.js

110 ms

combined.min.js

combined.min.js

238 ms

colloquy-logo-tag.svg

colloquy-logo-tag.svg

67 ms

colloquy-logo-white.svg

colloquy-logo-white.svg

63 ms

loading.gif

loading.gif

67 ms

gtm.js

gtm.js

204 ms

80

80

187 ms

80

80

185 ms

80

80

231 ms

80

80

230 ms

80

80

231 ms

80

80

297 ms

FrutigerCondensed.woff

FrutigerCondensed.woff

226 ms

FrutigerBoldCondensed.woff

FrutigerBoldCondensed.woff

229 ms

FrutigerBlackCondensed.woff

FrutigerBlackCondensed.woff

291 ms

icomoon.woff

icomoon.woff

253 ms

85

85

201 ms

85

85

200 ms

85

85

262 ms

home-news-item-no-img.svg

home-news-item-no-img.svg

222 ms

80

80

261 ms

80

80

262 ms

80

80

328 ms

80

80

324 ms

menu-accent.svg

menu-accent.svg

323 ms

widgets.js

widgets.js

140 ms

08b1672f-a9b2-43e2-addd-d8fcdf0b6c00.js

08b1672f-a9b2-43e2-addd-d8fcdf0b6c00.js

87 ms

analytics.js

analytics.js

113 ms

fbevents.js

fbevents.js

174 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

30 ms

80

80

131 ms

80

80

131 ms

80

80

130 ms

80

80

132 ms

FrutigerRoman.woff

FrutigerRoman.woff

125 ms

collect

collect

37 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

35 ms

26 ms

jot

jot

92 ms

Accessibility Review

colloquy.com accessibility score

99

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

Best Practices

colloquy.com best practices score

67

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

colloquy.com SEO score

76

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

High

robots.txt is not valid

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

colloquy.com

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