Tools & Wizards About Us
who.me screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

who.me

Touch Screens, Inc. | 435.673.5455 | Touch Screens Inc.

Page Load Speed

1.9 sec in total

First Response

44 ms

Resources Loaded

1.7 sec

Page Rendered

244 ms

who.me screenshot

About Website

Visit who.me now to see the best up-to-date Who content and also check out these interesting facts you probably never knew about who.me

We sell touch computers, touch displays, elo touch, keyboards and touch PCs. Browse our catalog and order.

Visit who.me

Key Findings

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

Performance Metrics

who.me performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value14.1 s

10/100

10%

Network Requests Diagram

who.me

44 ms

www.touchwindow.com

468 ms

clientside.mvc

71 ms

clientside.mvc

129 ms

clientside.mvc

190 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Who.me, 73% (36 requests) were made to Touchwindow.com and 6% (3 requests) were made to S3-us-west-2.amazonaws.com. The less responsive or slowest element that took the longest time to load (468 ms) relates to the external source Touchwindow.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.8 kB (19%)

Content Size

640.1 kB

After Optimization

521.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Who.me main page is 640.1 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. 50% of websites need less resources to load. Images take 402.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 38.7 kB

  • Original 48.9 kB
  • After minification 48.4 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. 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 38.7 kB or 79% of the original size.

Image Optimization

-14%

Potential reduce by 57.6 kB

  • Original 402.6 kB
  • After minification 345.0 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, Who needs image optimization as it can save up to 57.6 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

-12%

Potential reduce by 22.5 kB

  • Original 188.6 kB
  • After minification 187.7 kB
  • After compression 166.2 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 22.5 kB or 12% 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 Who. 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

who.me

who.me

44 ms

www.touchwindow.com

www.touchwindow.com

468 ms

clientside.mvc

clientside.mvc

71 ms

clientside.mvc

clientside.mvc

129 ms

clientside.mvc

clientside.mvc

190 ms

all.php

all.php

411 ms

css

css

52 ms

js

js

83 ms

clientside.mvc

clientside.mvc

206 ms

vendor.min.js

vendor.min.js

287 ms

plugins.js

plugins.js

287 ms

scripts.js

scripts.js

287 ms

intersection-observer.js

intersection-observer.js

53 ms

1.js

1.js

43 ms

reb2b.js.gz

reb2b.js.gz

285 ms

t21_132x91.jpg

t21_132x91.jpg

67 ms

img_credit-cards.png

img_credit-cards.png

99 ms

instantssl_trust_seal_sm_118x32.png

instantssl_trust_seal_sm_118x32.png

99 ms

amazon-connect-chat-interface-client.js

amazon-connect-chat-interface-client.js

101 ms

gtm.js

gtm.js

55 ms

Suivant.woff

Suivant.woff

87 ms

ElegantIcons.woff

ElegantIcons.woff

223 ms

jquery.menu-aim.js

jquery.menu-aim.js

75 ms

analytics.js

analytics.js

56 ms

jquery.slick.min.js

jquery.slick.min.js

80 ms

client.json

client.json

235 ms

client.json

client.json

280 ms

M150t-2.jpg

M150t-2.jpg

70 ms

Ascent.jpg

Ascent.jpg

153 ms

215ISeriesIntelWithStand.jpg

215ISeriesIntelWithStand.jpg

71 ms

ET5XWindows.jpg

ET5XWindows.jpg

103 ms

tmt88vlores.jpg

tmt88vlores.jpg

121 ms

GenericCashDrawer-14-3t.jpg

GenericCashDrawer-14-3t.jpg

135 ms

scanner.jpg

scanner.jpg

137 ms

Kiosk-Podium2.gif

Kiosk-Podium2.gif

175 ms

LC8710.png

LC8710.png

257 ms

kb1700loresbeige.jpg

kb1700loresbeige.jpg

199 ms

poledisplays.jpg

poledisplays.jpg

201 ms

I32ZI.jpg

I32ZI.jpg

214 ms

msr.jpg

msr.jpg

214 ms

ELR5220-WT-KRXB-QG.jpg

ELR5220-WT-KRXB-QG.jpg

242 ms

StarofLife.jpg

StarofLife.jpg

262 ms

StarmPOP.jpg

StarmPOP.jpg

264 ms

TLP808TELTV.jpg

TLP808TELTV.jpg

285 ms

AudioSpotLightSmall.jpg

AudioSpotLightSmall.jpg

282 ms

siglite_1x5_medium.png

siglite_1x5_medium.png

311 ms

ribbonsforpos.jpg

ribbonsforpos.jpg

327 ms

visit

visit

268 ms

visit

visit

68 ms

Accessibility Review

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

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

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

Best Practices

who.me best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

who.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 Who.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 Who.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

who.me

Open Graph description is not detected on the main page of Who. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: