Tools & Wizards About Us

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fongo.com

Fongo | Canada’s Affordable Communications Provider

Page Load Speed

2.9 sec in total

First Response

111 ms

Resources Loaded

2.4 sec

Page Rendered

361 ms

About Website

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

Founded and based out of Waterloo, Ontario, Fongo provides Canadians with low-cost, personal and small business communication solutions.

Visit fongo.com

Key Findings

We analyzed Fongo.com page load time and found that the first response time was 111 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fongo.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.122

84/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

fongo.com

111 ms

www.fongo.com

114 ms

base.css

24 ms

layout.css

40 ms

general-styles.css

42 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 51% of them (41 requests) were addressed to the original Fongo.com, 10% (8 requests) were made to Apis.google.com and 6% (5 requests) were made to Static.licdn.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fongo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (20%)

Content Size

5.6 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fongo.com main page is 5.6 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. 70% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 155.2 kB

  • Original 198.8 kB
  • After minification 187.3 kB
  • After compression 43.5 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 155.2 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 88.6 kB

  • Original 4.1 MB
  • After minification 4.0 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. Fongo images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 771.5 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 360.3 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 771.5 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 98.3 kB

  • Original 119.5 kB
  • After minification 102.1 kB
  • After compression 21.2 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. Fongo.com needs all CSS files to be minified and compressed as it can save up to 98.3 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fongo.com accessibility score

96

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.

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

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

fongo.com SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fongo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fongo.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 Fongo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: