Tools & Wizards About Us
recognizeapp.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

recognizeapp.com

Social & Integrated, Employee Recognition Program - Recognize

Page Load Speed

4.1 sec in total

First Response

488 ms

Resources Loaded

3.1 sec

Page Rendered

527 ms

recognizeapp.com screenshot

About Website

Welcome to recognizeapp.com homepage info - get ready to check Recognize App best content for United States right away, or after learning these important things about recognizeapp.com

Improving company culture through employee recognition, rewards, surveys, nominations inside Microsoft 365.

Visit recognizeapp.com

Key Findings

We analyzed Recognizeapp.com page load time and found that the first response time was 488 ms and then it took 3.6 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

recognizeapp.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value39,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.083

94/100

15%

TTI (Time to Interactive)

Value53.0 s

0/100

10%

Network Requests Diagram

recognizeapp.com

488 ms

2418500345.js

345 ms

marketing-pages-6ee611cd29c0c4683d17aafc0d036a68.css

546 ms

marketing-70b7ff651f6cf8cbcb719c7cf4a9499e.js

765 ms

event

41 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 10% of them (5 requests) were addressed to the original Recognizeapp.com, 36% (18 requests) were made to D20lvaubx29wwe.cloudfront.net and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source D20lvaubx29wwe.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (64%)

Content Size

2.5 MB

After Optimization

904.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Recognizeapp.com main page is 2.5 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. 40% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 35.1 kB

  • Original 45.3 kB
  • After minification 37.3 kB
  • After compression 10.1 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 7.9 kB, which is 18% 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 35.1 kB or 78% of the original size.

Image Optimization

-14%

Potential reduce by 64.4 kB

  • Original 450.7 kB
  • After minification 386.3 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. Obviously, Recognize App needs image optimization as it can save up to 64.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 408.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 1.1 MB or 72% of the original size.

CSS Optimization

-81%

Potential reduce by 415.8 kB

  • Original 515.5 kB
  • After minification 512.4 kB
  • After compression 99.7 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. Recognizeapp.com needs all CSS files to be minified and compressed as it can save up to 415.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (32%)

Requests Now

44

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

recognizeapp.com

recognizeapp.com

488 ms

2418500345.js

2418500345.js

345 ms

marketing-pages-6ee611cd29c0c4683d17aafc0d036a68.css

marketing-pages-6ee611cd29c0c4683d17aafc0d036a68.css

546 ms

marketing-70b7ff651f6cf8cbcb719c7cf4a9499e.js

marketing-70b7ff651f6cf8cbcb719c7cf4a9499e.js

765 ms

event

event

41 ms

css

css

74 ms

analytics.min.js

analytics.min.js

208 ms

hotjar-124244.js

hotjar-124244.js

500 ms

bruce.jpg

bruce.jpg

800 ms

happy-4f784d8c93395a6aca6c535fe797c1a7.png

happy-4f784d8c93395a6aca6c535fe797c1a7.png

328 ms

goodway.jpg

goodway.jpg

621 ms

leonardo.jpg

leonardo.jpg

579 ms

tessa.jpg

tessa.jpg

586 ms

speedometer-8c127c7abf09e72240ff763e241d1797.png

speedometer-8c127c7abf09e72240ff763e241d1797.png

327 ms

flag-d9d30c63b8af8dbae234f23c0dd4c9ae.png

flag-d9d30c63b8af8dbae234f23c0dd4c9ae.png

361 ms

ios7-pulse-a888bf4c7735defd926f3d49f229ddb4.png

ios7-pulse-a888bf4c7735defd926f3d49f229ddb4.png

361 ms

ios7-people-e2a79a13bec67948573d047d3b3442ef.png

ios7-people-e2a79a13bec67948573d047d3b3442ef.png

789 ms

key-43a31a84e37721414058d01b770eb9c0.png

key-43a31a84e37721414058d01b770eb9c0.png

797 ms

slack-2e01c6acd995468fe066ae77a0b7ae5e.png

slack-2e01c6acd995468fe066ae77a0b7ae5e.png

788 ms

navigate-d456d2115bf7469d6ec52ae342e63585.png

navigate-d456d2115bf7469d6ec52ae342e63585.png

487 ms

ios7-contact-3d3fe052f63c0fb5f17cdc1f701a71de.png

ios7-contact-3d3fe052f63c0fb5f17cdc1f701a71de.png

488 ms

podium-49658302d74b8f328f87863058bb3c0f.png

podium-49658302d74b8f328f87863058bb3c0f.png

797 ms

university-61819b4aff5e17fa34f0cc12b17ba99e.png

university-61819b4aff5e17fa34f0cc12b17ba99e.png

860 ms

iphone-0b95a30e3c7c460b63af043bac8da090.png

iphone-0b95a30e3c7c460b63af043bac8da090.png

847 ms

ios7-chatbubble-b86f73b347398a7a3b2c914c9cc04a81.png

ios7-chatbubble-b86f73b347398a7a3b2c914c9cc04a81.png

1060 ms

trophy-d7e697586b01c30cfb585783d9de7fad.png

trophy-d7e697586b01c30cfb585783d9de7fad.png

1056 ms

logo-mark-ios-1c076aac166ff58948676defea305e76.png

logo-mark-ios-1c076aac166ff58948676defea305e76.png

1026 ms

movement-a9d45b2dc2bec86ce09d2e28b5b9fb21.png

movement-a9d45b2dc2bec86ce09d2e28b5b9fb21.png

1133 ms

iframe_api

iframe_api

373 ms

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

320 ms

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

330 ms

ga.js

ga.js

190 ms

main.js

main.js

472 ms

p

p

799 ms

tracker.js

tracker.js

73 ms

www-widgetapi.js

www-widgetapi.js

71 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

64 ms

pv

pv

66 ms

collect

collect

76 ms

2eYHSBUSkcA

2eYHSBUSkcA

70 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

16 ms

www-embed-player.js

www-embed-player.js

34 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

114 ms

ad_status.js

ad_status.js

110 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

95 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

95 ms

update.html

update.html

70 ms

blips

blips

172 ms

config

config

6 ms

widget_v2.134.js

widget_v2.134.js

29 ms

Accessibility Review

recognizeapp.com accessibility score

71

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

recognizeapp.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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

recognizeapp.com SEO score

93

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

Image elements do not have [alt] attributes

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 Recognizeapp.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 Recognizeapp.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

recognizeapp.com

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