Tools & Wizards About Us
forum.fongo.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

forum.fongo.com

Fongo Community Forums • Index page

Page Load Speed

2.3 sec in total

First Response

377 ms

Resources Loaded

1.6 sec

Page Rendered

259 ms

forum.fongo.com screenshot

About Website

Click here to check amazing Forum Fongo content for Canada. Otherwise, check out these important facts you probably never knew about forum.fongo.com

Fongo powers free calling solutions for a number of brands. This forum includes information and tips on all of those offerings. Note that your specific services may vary based on the specific Fongo ...

Visit forum.fongo.com

Key Findings

We analyzed Forum.fongo.com page load time and found that the first response time was 377 ms and then it took 1.9 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

forum.fongo.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

forum.fongo.com

377 ms

plusone.js

96 ms

styleswitcher.js

45 ms

forum_fn.js

44 ms

smartbanner.js

46 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 33% of them (27 requests) were addressed to the original Forum.fongo.com, 12% (10 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 (419 ms) relates to the external source Apis.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.9 kB (55%)

Content Size

538.7 kB

After Optimization

241.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 54.4 kB

  • Original 65.7 kB
  • After minification 55.6 kB
  • After compression 11.2 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 10.1 kB, which is 15% 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 54.4 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 3.9 kB

  • Original 63.2 kB
  • After minification 59.2 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. Forum Fongo images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 192.8 kB

  • Original 353.8 kB
  • After minification 343.6 kB
  • After compression 161.0 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 192.8 kB or 54% of the original size.

CSS Optimization

-82%

Potential reduce by 45.8 kB

  • Original 56.1 kB
  • After minification 54.1 kB
  • After compression 10.3 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. Forum.fongo.com needs all CSS files to be minified and compressed as it can save up to 45.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (70%)

Requests Now

76

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forum.fongo.com

forum.fongo.com

377 ms

plusone.js

plusone.js

96 ms

styleswitcher.js

styleswitcher.js

45 ms

forum_fn.js

forum_fn.js

44 ms

smartbanner.js

smartbanner.js

46 ms

style.php

style.php

150 ms

normal.css

normal.css

45 ms

adsbygoogle.js

adsbygoogle.js

5 ms

in.js

in.js

5 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

analytics.js

analytics.js

65 ms

sdk.js

sdk.js

122 ms

widgets.js

widgets.js

238 ms

secureAnonymousFramework

secureAnonymousFramework

138 ms

platform.js

platform.js

93 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

136 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

230 ms

follow

follow

419 ms

fpl_forum_logos_fongo.png

fpl_forum_logos_fongo.png

126 ms

icon_textbox_search.gif

icon_textbox_search.gif

80 ms

bg_button.gif

bg_button.gif

80 ms

icon_home.gif

icon_home.gif

80 ms

icon_fontsize.gif

icon_fontsize.gif

79 ms

icon_faq.gif

icon_faq.gif

80 ms

icon_register.gif

icon_register.gif

221 ms

icon_logout.gif

icon_logout.gif

221 ms

forum_read_locked.gif

forum_read_locked.gif

221 ms

icon_topic_latest.gif

icon_topic_latest.gif

220 ms

forum_read.gif

forum_read.gif

221 ms

ios.png

ios.png

221 ms

android.png

android.png

281 ms

blackberry.png

blackberry.png

280 ms

fongo_faces_butterfly.png

fongo_faces_butterfly.png

281 ms

home_phone.png

home_phone.png

280 ms

fongo_desktop.png

fongo_desktop.png

279 ms

bullet.square.silver.png

bullet.square.silver.png

280 ms

ca-pub-8920538685908747.js

ca-pub-8920538685908747.js

288 ms

zrt_lookup.html

zrt_lookup.html

268 ms

show_ads_impl.js

show_ads_impl.js

106 ms

collect

collect

55 ms

ads

ads

360 ms

148 ms

osd.js

osd.js

86 ms

xd_arbiter.php

xd_arbiter.php

125 ms

xd_arbiter.php

xd_arbiter.php

208 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

196 ms

postmessageRelay

postmessageRelay

81 ms

print.css

print.css

36 ms

medium.css

medium.css

34 ms

api.js

api.js

54 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

91 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

68 ms

large.css

large.css

37 ms

rs=AGLTcCMMqqsIc6OcjXFVuYh2RauPSc-8kA

rs=AGLTcCMMqqsIc6OcjXFVuYh2RauPSc-8kA

13 ms

rs=AGLTcCMRrQOl3aog0WfiN8cQPcADd6GNiA

rs=AGLTcCMRrQOl3aog0WfiN8cQPcADd6GNiA

41 ms

rs=AGLTcCPiVA6ceimGGnDWBM6c15EqWRK-mA

rs=AGLTcCPiVA6ceimGGnDWBM6c15EqWRK-mA

72 ms

css

css

111 ms

m_js_controller.js

m_js_controller.js

71 ms

abg.js

abg.js

74 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

127 ms

d-QWLnp4didxos_6urzFtg.woff

d-QWLnp4didxos_6urzFtg.woff

157 ms

vxNK-E6B13CyehuDCmvQvw.woff

vxNK-E6B13CyehuDCmvQvw.woff

185 ms

follow_button.6a78875565a912489e9aef879c881358.en-gb.html

follow_button.6a78875565a912489e9aef879c881358.en-gb.html

42 ms

favicon

favicon

82 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

26 ms

s

s

16 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

60 ms

x_button_blue2.png

x_button_blue2.png

7 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

4 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

64 ms

jot

jot

107 ms

ui

ui

51 ms

xdrpc.html

xdrpc.html

28 ms

like.php

like.php

67 ms

followcompany

followcompany

67 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

197 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

211 ms

css

css

34 ms

anonymoususerspace

anonymoususerspace

20 ms

js

js

54 ms

css

css

91 ms

js

js

96 ms

sprite_connect_v15.png

sprite_connect_v15.png

10 ms

Accessibility Review

forum.fongo.com accessibility score

81

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[accesskey] values are not unique

High

Heading elements are not in a sequentially-descending order

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

<frame> or <iframe> elements do not have a title

Best Practices

forum.fongo.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

forum.fongo.com SEO score

81

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

    EN

  • Encoding

    UTF-8

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

forum.fongo.com

Open Graph data is detected on the main page of Forum Fongo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: