Tools & Wizards About Us
try.evoice.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

try.evoice.com

Try eVoice - A virtual phone system that leaves a lasting impression

Page Load Speed

3.2 sec in total

First Response

244 ms

Resources Loaded

2.6 sec

Page Rendered

405 ms

try.evoice.com screenshot

About Website

Click here to check amazing Try EVoice content for United States. Otherwise, check out these important facts you probably never knew about try.evoice.com

An advanced virtual phone system that is easy to set up and use. Phone numbers, conference calling, auto attendants and more.

Visit try.evoice.com

Key Findings

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

Performance Metrics

try.evoice.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

try.evoice.com

244 ms

try.evoice.com

222 ms

7e31b0fe-d091-4f0f-b720-46570ed33134.css

215 ms

158294bb-b27b-4dc4-9e6b-913addc0355f.css

110 ms

7d9895e6-818d-46ad-b64e-ff0dfe2c8fdf.css

218 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Try.evoice.com, 17% (17 requests) were made to Hb.wpmucdn.com and 8% (8 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (761 ms) relates to the external source D3cxv97fi8q177.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 449.6 kB (50%)

Content Size

893.9 kB

After Optimization

444.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Try.evoice.com main page is 893.9 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. 70% of websites need less resources to load. Javascripts take 429.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 122.8 kB

  • Original 148.4 kB
  • After minification 139.4 kB
  • After compression 25.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 122.8 kB or 83% of the original size.

JavaScript Optimization

-9%

Potential reduce by 37.8 kB

  • Original 429.3 kB
  • After minification 429.3 kB
  • After compression 391.5 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.

CSS Optimization

-91%

Potential reduce by 289.0 kB

  • Original 316.2 kB
  • After minification 47.7 kB
  • After compression 27.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. Try.evoice.com needs all CSS files to be minified and compressed as it can save up to 289.0 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (91%)

Requests Now

81

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

try.evoice.com

try.evoice.com

244 ms

try.evoice.com

try.evoice.com

222 ms

7e31b0fe-d091-4f0f-b720-46570ed33134.css

7e31b0fe-d091-4f0f-b720-46570ed33134.css

215 ms

158294bb-b27b-4dc4-9e6b-913addc0355f.css

158294bb-b27b-4dc4-9e6b-913addc0355f.css

110 ms

7d9895e6-818d-46ad-b64e-ff0dfe2c8fdf.css

7d9895e6-818d-46ad-b64e-ff0dfe2c8fdf.css

218 ms

post-8691.css

post-8691.css

64 ms

post-9044.css

post-9044.css

273 ms

dynamic-mobmenu.css

dynamic-mobmenu.css

234 ms

css

css

103 ms

f5cc38a5-90f3-4268-9b4c-4cb3ba4b8e7e.css

f5cc38a5-90f3-4268-9b4c-4cb3ba4b8e7e.css

92 ms

css

css

205 ms

37c9a8ec-3350-4d04-8f76-6207c3dc5b0e.css

37c9a8ec-3350-4d04-8f76-6207c3dc5b0e.css

88 ms

cdd0f604-da27-4275-8291-0ac3157c818d.js

cdd0f604-da27-4275-8291-0ac3157c818d.js

208 ms

4949e227-fa26-471d-b6f4-6997fdc8fb18.js

4949e227-fa26-471d-b6f4-6997fdc8fb18.js

208 ms

ef369db8-8f90-443f-b74e-81ac0a300f87.css

ef369db8-8f90-443f-b74e-81ac0a300f87.css

99 ms

4bc9b295-54c1-432b-8244-98f305256c4f.css

4bc9b295-54c1-432b-8244-98f305256c4f.css

208 ms

dba37d53-ec11-4a7e-a59a-250efc7c312d.js

dba37d53-ec11-4a7e-a59a-250efc7c312d.js

211 ms

5928e198-21ee-477c-b97f-0d5fe512bea9.js

5928e198-21ee-477c-b97f-0d5fe512bea9.js

215 ms

wp-polyfill.min.js

wp-polyfill.min.js

202 ms

bac38205-dacb-48e2-91ac-850c3620cedf.js

bac38205-dacb-48e2-91ac-850c3620cedf.js

215 ms

vue.min.js

vue.min.js

253 ms

e570f339-ca87-4c88-8cd9-9d747dc21951.js

e570f339-ca87-4c88-8cd9-9d747dc21951.js

208 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

231 ms

webpack.runtime.min.js

webpack.runtime.min.js

198 ms

e74c6409-e40a-4e35-aa37-2a79707e9d10.js

e74c6409-e40a-4e35-aa37-2a79707e9d10.js

214 ms

51ada465-27ce-4d48-8500-d54127ad7b9b.js

51ada465-27ce-4d48-8500-d54127ad7b9b.js

210 ms

e28e9b6e-d7f3-4edf-993e-5ca7b822a6eb.js

e28e9b6e-d7f3-4edf-993e-5ca7b822a6eb.js

215 ms

core.min.js

core.min.js

206 ms

c5fd22fb-8950-48a6-aede-6d49cef91f7d.js

c5fd22fb-8950-48a6-aede-6d49cef91f7d.js

210 ms

snippet.js

snippet.js

198 ms

39506695.js

39506695.js

200 ms

gtm.js

gtm.js

197 ms

j.php

j.php

194 ms

waves-blue-left-1-1.svg

waves-blue-left-1-1.svg

136 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

104 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

104 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

350 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

354 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

498 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

498 ms

fa-solid-900.woff

fa-solid-900.woff

355 ms

fa-solid-900.woff

fa-solid-900.woff

354 ms

fa-regular-400.woff

fa-regular-400.woff

353 ms

fa-regular-400.woff

fa-regular-400.woff

352 ms

v.gif

v.gif

367 ms

va-985d4634f2576919c23c4bbdaa369d79.js

va-985d4634f2576919c23c4bbdaa369d79.js

566 ms

track-985d4634f2576919c23c4bbdaa369d79.js

track-985d4634f2576919c23c4bbdaa369d79.js

372 ms

opa-f2c825d123a0ff3a4ae0c9b1c9165f29.js

opa-f2c825d123a0ff3a4ae0c9b1c9165f29.js

373 ms

js

js

288 ms

js

js

404 ms

js

js

473 ms

analytics.js

analytics.js

719 ms

destination

destination

333 ms

destination

destination

360 ms

destination

destination

387 ms

insight.min.js

insight.min.js

699 ms

tune.js

tune.js

738 ms

mediasource-A36875-01e1-4807-b56c-f8ae5a0e967e1-c-1607.js

mediasource-A36875-01e1-4807-b56c-f8ae5a0e967e1-c-1607.js

761 ms

bat.js

bat.js

699 ms

js

js

735 ms

tc.min.js

tc.min.js

729 ms

fbevents.js

fbevents.js

651 ms

teads-fellow.js

teads-fellow.js

729 ms

pixie.js

pixie.js

694 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

693 ms

banner.js

banner.js

631 ms

39506695.js

39506695.js

631 ms

worker-70faafffa0475802f5ee03ca5ff74179.js

worker-70faafffa0475802f5ee03ca5ff74179.js

105 ms

settings.js

settings.js

86 ms

insight_tag_errors.gif

insight_tag_errors.gif

130 ms

linkid.js

linkid.js

51 ms

ca.html

ca.html

150 ms

pixel

pixel

37 ms

collect

collect

17 ms

collect

collect

37 ms

pixel

pixel

26 ms

ga-audiences

ga-audiences

41 ms

match-result

match-result

8 ms

pixel

pixel

288 ms

pixel

pixel

78 ms

Pug

Pug

222 ms

cksync.php

cksync.php

248 ms

258 ms

360947.gif

360947.gif

253 ms

rocketfuel_sync

rocketfuel_sync

282 ms

sync

sync

217 ms

g.pixel

g.pixel

221 ms

collect

collect

21 ms

settings.js

settings.js

77 ms

demconf.jpg

demconf.jpg

10 ms

sd

sd

14 ms

bounce

bounce

17 ms

cm

cm

16 ms

sync

sync

21 ms

pixel

pixel

133 ms

rum

rum

24 ms

pixel

pixel

71 ms

sync

sync

51 ms

pixel

pixel

69 ms

sync

sync

36 ms

Accessibility Review

try.evoice.com accessibility score

96

Accessibility Issues

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

try.evoice.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

High

Page has valid source maps

SEO Factors

try.evoice.com SEO score

80

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Try.evoice.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 Try.evoice.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

try.evoice.com

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