Access local-analytics.wyzetalk.com. Unleashing the Future of Employee Engagement

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value10.5 s

8/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

local-analytics.wyzetalk.com

199 ms

www.wyzetalk.com

439 ms

gtm.js

95 ms

style.min.css

67 ms

search-filter.min.css

80 ms

Our browser made a total of 141 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Local-analytics.wyzetalk.com, 72% (101 requests) were made to Www-cdn.wyzetalk.com and 6% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (721 ms) relates to the external source Fonts.gstatic.com.

Content Size

1.6 MB

After Optimization

1.2 MB

In fact, the total size of Local-analytics.wyzetalk.com main page is 1.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. 80% 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. Javascripts take 679.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 131.2 kB

Original 158.0 kB
After minification 124.3 kB
After compression 26.8 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 33.7 kB, which is 21% 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 131.2 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 10.3 kB

Original 671.9 kB
After minification 661.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. Local Analytics Wyzetalk images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 212.9 kB

Original 679.7 kB
After minification 679.2 kB
After compression 466.7 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 212.9 kB or 31% of the original size.

CSS Optimization

-12%

Potential reduce by 6.9 kB

Original 59.0 kB
After minification 59.0 kB
After compression 52.1 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. Local-analytics.wyzetalk.com needs all CSS files to be minified and compressed as it can save up to 6.9 kB or 12% of the original size.

Requests Now

130

After Optimization

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

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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/).

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 Local-analytics.wyzetalk.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 Local-analytics.wyzetalk.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

local-analytics.wyzetalk.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Unleashing the Future of Employee Engagement | Wyzetalk

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

local-analytics.wyzetalk.com

www.wyzetalk.com

gtm.js

style.min.css

search-filter.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

local-analytics.wyzetalk.com

www.wyzetalk.com

gtm.js

style.min.css

search-filter.min.css

app.css

slick.css

lity.min.css

slick-theme.css

jquery.min.js

jquery-migrate.min.js

js.cookie.js

handl-utm-grabber.js

search-filter-build.min.js

chosen.jquery.min.js

app.js

tags.js

8224001.js

basic.min.css

theme-ie11.min.css

theme.min.css

core.min.js

datepicker.min.js

slick.min.js

lity.min.js

wp-polyfill-inert.min.js

regenerator-runtime.min.js

wp-polyfill.min.js

dom-ready.min.js

hooks.min.js

i18n.min.js

a11y.min.js

jquery.json.min.js

gravityforms.min.js

utils.min.js

vendor-theme.min.js

scripts-theme.min.js

select2.min.js

autocompleteaddress.js

gf-ipm.js

intlTelInput-jquery.js

intlTelInput.js

js