Tools & Wizards About Us
zello.me screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

zello.me

Zello | The Most Reliable Push-to-Talk Walkie Talkie App

Page Load Speed

1.4 sec in total

First Response

34 ms

Resources Loaded

450 ms

Page Rendered

934 ms

zello.me screenshot

About Website

Click here to check amazing Zello content. Otherwise, check out these important facts you probably never knew about zello.me

Stay connected with your team using Zello - the leading push-to-talk app for frontline communication. Download Zello for work and get PTT walkie talkie and radio features. Visit us now.

Visit zello.me

Key Findings

We analyzed Zello.me page load time and found that the first response time was 34 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

zello.me performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

zello.me

34 ms

zello.com

53 ms

web-font-loader.js

22 ms

styles.css

54 ms

keen-slider.min.js

38 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Zello.me, 51% (21 requests) were made to Res.cloudinary.com and 32% (13 requests) were made to Zello.com. The less responsive or slowest element that took the longest time to load (236 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.2 kB (68%)

Content Size

85.6 kB

After Optimization

27.4 kB

  • HTML
  • JavaScript

In fact, the total size of Zello.me main page is 85.6 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. 30% of websites need less resources to load. HTML takes 80.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 57.8 kB

  • Original 80.2 kB
  • After minification 79.3 kB
  • After compression 22.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. 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 57.8 kB or 72% of the original size.

JavaScript Optimization

-8%

Potential reduce by 453 B

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

Requests Breakdown

Number of requests can be reduced by 15 (43%)

Requests Now

35

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zello.me

zello.me

34 ms

zello.com

zello.com

53 ms

web-font-loader.js

web-font-loader.js

22 ms

styles.css

styles.css

54 ms

keen-slider.min.js

keen-slider.min.js

38 ms

scroll-lock.min.js

scroll-lock.min.js

35 ms

nav.js

nav.js

35 ms

dropdown.js

dropdown.js

40 ms

localizer.js

localizer.js

39 ms

lazysizes.min.js

lazysizes.min.js

128 ms

webfont.js

webfont.js

146 ms

photo--construction-3.webp

photo--construction-3.webp

192 ms

client--pepsico-padded.svg

client--pepsico-padded.svg

187 ms

client--swissport-padded.svg

client--swissport-padded.svg

191 ms

client--latam-padded.svg

client--latam-padded.svg

189 ms

client--sams-padded.svg

client--sams-padded.svg

186 ms

client--oreilly-padded.svg

client--oreilly-padded.svg

167 ms

client--hyatt-padded.svg

client--hyatt-padded.svg

195 ms

client--bechtel-new-padded.svg

client--bechtel-new-padded.svg

203 ms

client--holcim-padded.svg

client--holcim-padded.svg

193 ms

ill--hardy-00_2x.webp

ill--hardy-00_2x.webp

235 ms

ill--dispatch-station-00_2x.webp

ill--dispatch-station-00_2x.webp

201 ms

ill--message-history-00_2x.webp

ill--message-history-00_2x.webp

236 ms

ill-break-free-03.webp

ill-break-free-03.webp

141 ms

ill-break-free-02.webp

ill-break-free-02.webp

140 ms

ill-break-free-01.webp

ill-break-free-01.webp

141 ms

appIcon--textured.webp

appIcon--textured.webp

151 ms

appIcon--iOS-120-contents.svg

appIcon--iOS-120-contents.svg

154 ms

appIcon--iOS-mask.svg

appIcon--iOS-mask.svg

144 ms

ill--accessories-00_2x.webp

ill--accessories-00_2x.webp

149 ms

photo--firefighters-3.webp

photo--firefighters-3.webp

216 ms

photo--nat-disaster-1.webp

photo--nat-disaster-1.webp

230 ms

icon--caret-right-body2.svg

icon--caret-right-body2.svg

41 ms

icon--caret-right-body1.svg

icon--caret-right-body1.svg

42 ms

icon--caret-right-body3.svg

icon--caret-right-body3.svg

41 ms

ui--select.svg

ui--select.svg

43 ms

css

css

64 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5a1PiKQ.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5a1PiKQ.ttf

21 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

33 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

53 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

53 ms

Accessibility Review

zello.me accessibility score

87

Accessibility Issues

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.

Best Practices

zello.me 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

High

Page has valid source maps

SEO Factors

zello.me SEO score

100

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

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 Zello.me 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 Zello.me 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

zello.me

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