Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

colloquy.info

Colloquy

Page Load Speed

1 sec in total

First Response

53 ms

Resources Loaded

885 ms

Page Rendered

86 ms

colloquy.info screenshot

About Website

Visit colloquy.info 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.info

Visit colloquy.info

Key Findings

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

Performance Metrics

colloquy.info performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

colloquy.info

53 ms

colloquy.app

365 ms

icon.png

466 ms

app-store.svg

386 ms

github.svg

316 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Colloquy.info, 80% (4 requests) were made to Colloquy.app. The less responsive or slowest element that took the longest time to load (466 ms) relates to the external source Colloquy.app.

Page Optimization Overview & Recommendations

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

Content Size

56.8 kB

After Optimization

47.6 kB

In fact, the total size of Colloquy.info main page is 56.8 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Images take 54.8 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 1.3 kB

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 705 B

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 1.3 kB or 65% of the original size.

Image Optimization

-14%

Potential reduce by 7.9 kB

  • Original 54.8 kB
  • After minification 46.9 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. Obviously, Colloquy needs image optimization as it can save up to 7.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Colloquy. According to our analytics all requests are already optimized.

Accessibility Review

colloquy.info accessibility score

62

Accessibility Issues

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

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

High

Links do not have a discernible name

Best Practices

colloquy.info best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

colloquy.info SEO score

85

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Colloquy.info 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Colloquy.info 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

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: