Tools & Wizards About Us
info.fonality.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

info.fonality.com

Why Sangoma - Sangoma Technologies

Page Load Speed

3.5 sec in total

First Response

261 ms

Resources Loaded

2.3 sec

Page Rendered

958 ms

info.fonality.com screenshot

About Website

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

Sangoma’s global footprint extends to millions of customers using our products and services in leading PBX, IVR, contact center, carrier network, and data communication applications.

Visit info.fonality.com

Key Findings

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

Performance Metrics

info.fonality.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,000 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

info.fonality.com

261 ms

netfortris.com

76 ms

www.netfortris.com

316 ms

309 ms

274 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Info.fonality.com, 76% (84 requests) were made to Sangoma.com and 12% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (471 ms) relates to the external source Px.ads.linkedin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.6 kB (27%)

Content Size

1.0 MB

After Optimization

752.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Info.fonality.com main page is 1.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 469.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 279.6 kB

  • Original 323.3 kB
  • After minification 307.7 kB
  • After compression 43.7 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 279.6 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 469.6 kB
  • After minification 469.6 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. Info Fonality images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 5 B

  • Original 238.6 kB
  • After minification 238.6 kB
  • After compression 238.6 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 84 (90%)

Requests Now

93

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

info.fonality.com

info.fonality.com

261 ms

netfortris.com

netfortris.com

76 ms

www.netfortris.com

www.netfortris.com

316 ms

309 ms

274 ms

uc-block.bundle.js

uc-block.bundle.js

52 ms

loader.js

loader.js

59 ms

wibergsweb188.css

wibergsweb188.css

70 ms

templates5.css

templates5.css

82 ms

bootstrap.min.css

bootstrap.min.css

70 ms

main.min.css

main.min.css

79 ms

css

css

69 ms

dashicons.min.css

dashicons.min.css

69 ms

variables-skeleton.min.css

variables-skeleton.min.css

72 ms

variables-full.min.css

variables-full.min.css

89 ms

common-skeleton.min.css

common-skeleton.min.css

96 ms

common-full.min.css

common-full.min.css

111 ms

tickets.min.css

tickets.min.css

93 ms

rsvp-v1.min.css

rsvp-v1.min.css

91 ms

front-end-styles.css

front-end-styles.css

97 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

119 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

118 ms

widget-base.min.css

widget-base.min.css

116 ms

frontend-lite.min.css

frontend-lite.min.css

121 ms

swiper.min.css

swiper.min.css

125 ms

post-8.css

post-8.css

136 ms

frontend-lite.min.css

frontend-lite.min.css

139 ms

uael-frontend.min.css

uael-frontend.min.css

174 ms

all.min.css

all.min.css

142 ms

v4-shims.min.css

v4-shims.min.css

162 ms

global.css

global.css

164 ms

post-237911.css

post-237911.css

171 ms

post-19.css

post-19.css

200 ms

post-26.css

post-26.css

169 ms

post-327088.css

post-327088.css

205 ms

rsvp.min.css

rsvp.min.css

204 ms

style.css

style.css

202 ms

ecs-style.css

ecs-style.css

206 ms

css

css

62 ms

jquery.min.js

jquery.min.js

204 ms

jquery-migrate.min.js

jquery-migrate.min.js

224 ms

wibergsweb196.js

wibergsweb196.js

227 ms

termageddon-usercentrics-ajax.min.js

termageddon-usercentrics-ajax.min.js

228 ms

v4-shims.min.js

v4-shims.min.js

228 ms

js

js

99 ms

e056f203c8.js

e056f203c8.js

64 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

204 ms

bundle.js

bundle.js

29 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

200 ms

widget-icon-list.min.css

widget-icon-list.min.css

178 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

177 ms

fluent-forms-elementor-widget.css

fluent-forms-elementor-widget.css

182 ms

post-288515.css

post-288515.css

191 ms

post-89.css

post-89.css

186 ms

api.js

api.js

17 ms

post-268764.css

post-268764.css

175 ms

post-286361.css

post-286361.css

179 ms

post-269180.css

post-269180.css

185 ms

post-268980.css

post-268980.css

192 ms

animations.min.css

animations.min.css

187 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

183 ms

ecs.js

ecs.js

171 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

267 ms

frontend.min.js

frontend.min.js

267 ms

rsvp.min.js

rsvp.min.js

262 ms

ticket-details.min.js

ticket-details.min.js

261 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

251 ms

new-tab.js

new-tab.js

249 ms

uael-nav-menu.min.js

uael-nav-menu.min.js

243 ms

jquery_resize.min.js

jquery_resize.min.js

225 ms

js_cookie.min.js

js_cookie.min.js

222 ms

uael-frontend.min.js

uael-frontend.min.js

287 ms

typed.min.js

typed.min.js

219 ms

rvticker.min.js

rvticker.min.js

258 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

257 ms

webpack.runtime.min.js

webpack.runtime.min.js

254 ms

frontend-modules.min.js

frontend-modules.min.js

253 ms

waypoints.min.js

waypoints.min.js

253 ms

core.min.js

core.min.js

256 ms

frontend.min.js

frontend.min.js

233 ms

ecspro.js

ecspro.js

232 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

232 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

229 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

226 ms

wp-polyfill.min.js

wp-polyfill.min.js

234 ms

hooks.min.js

hooks.min.js

229 ms

i18n.min.js

i18n.min.js

227 ms

frontend.min.js

frontend.min.js

220 ms

elements-handlers.min.js

elements-handlers.min.js

240 ms

gtm.js

gtm.js

97 ms

sangoma-logo-1.svg

sangoma-logo-1.svg

173 ms

sangoma-suite-logo_White-and-Blue.svg

sangoma-suite-logo_White-and-Blue.svg

199 ms

GettyImages-617575248-scaled-1-1024x711.jpg

GettyImages-617575248-scaled-1-1024x711.jpg

202 ms

Sangoma-HSV-Office-Huntsville-1024x576.png

Sangoma-HSV-Office-Huntsville-1024x576.png

408 ms

GettyImages-869282952-1-scaled-1-1024x683.jpg

GettyImages-869282952-1-scaled-1-1024x683.jpg

203 ms

GettyImages-938516442-scaled-1-1024x684.jpg

GettyImages-938516442-scaled-1-1024x684.jpg

201 ms

insight.min.js

insight.min.js

144 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf

235 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaE0lP.ttf

396 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaE0lP.ttf

433 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaE0lP.ttf

432 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lP.ttf

430 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf

431 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aE0lP.ttf

431 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

431 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

434 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

434 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

432 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

433 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

433 ms

insight_tag_errors.gif

insight_tag_errors.gif

471 ms

Accessibility Review

info.fonality.com accessibility score

94

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

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

Links do not have a discernible name

Best Practices

info.fonality.com best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

info.fonality.com SEO score

99

Search Engine Optimization Advices

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 Info.fonality.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 Info.fonality.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

info.fonality.com

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