Tools & Wizards About Us
tmesys.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

tmesys.com

Pharmacy Locator

Page Load Speed

7 sec in total

First Response

166 ms

Resources Loaded

6.7 sec

Page Rendered

118 ms

tmesys.com screenshot

About Website

Welcome to tmesys.com homepage info - get ready to check Tmesys best content right away, or after learning these important things about tmesys.com

"Find the pharmacy closest to you by searching our network. Tmesys® the nationwide retail pharmacy network for Optum includes nearly 70,000 pharmacies."

Visit tmesys.com

Key Findings

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

Performance Metrics

tmesys.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

tmesys.com

166 ms

pharmacy-locator

419 ms

flexslider.css

129 ms

css

26 ms

css

38 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tmesys.com, 42% (26 requests) were made to Helioscomp.com and 34% (21 requests) were made to Www-sf.talispoint.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Helioscomp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (76%)

Content Size

1.5 MB

After Optimization

376.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tmesys.com main page is 1.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 806.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 37.1 kB

  • Original 46.9 kB
  • After minification 40.0 kB
  • After compression 9.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 6.9 kB, which is 15% 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 37.1 kB or 79% of the original size.

Image Optimization

-15%

Potential reduce by 3.4 kB

  • Original 22.7 kB
  • After minification 19.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, Tmesys needs image optimization as it can save up to 3.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 550.1 kB

  • Original 806.3 kB
  • After minification 751.8 kB
  • After compression 256.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 550.1 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 577.2 kB

  • Original 668.7 kB
  • After minification 561.8 kB
  • After compression 91.5 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. Tmesys.com needs all CSS files to be minified and compressed as it can save up to 577.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (62%)

Requests Now

60

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tmesys.com

tmesys.com

166 ms

pharmacy-locator

pharmacy-locator

419 ms

flexslider.css

flexslider.css

129 ms

css

css

26 ms

css

css

38 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

337 ms

layout_transformations.css

layout_transformations.css

306 ms

Reset.css

Reset.css

98 ms

Layout.css

Layout.css

288 ms

PMI.css

PMI.css

161 ms

Phone.css

Phone.css

173 ms

WebResource.axd

WebResource.axd

168 ms

WebResource.axd

WebResource.axd

167 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

467 ms

ScriptResource.axd

ScriptResource.axd

231 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

2894 ms

MainNavigation.js

MainNavigation.js

349 ms

element.js

element.js

33 ms

jquery.fitvids.js

jquery.fitvids.js

314 ms

jquery.sticky.custom.js

jquery.sticky.custom.js

314 ms

Site.js

Site.js

314 ms

heliostm-anoptumcompany-rgb-web-header.png

heliostm-anoptumcompany-rgb-web-header.png

100 ms

heliostm-anoptumcompany-rgb-reverse-white-web-footer.png

heliostm-anoptumcompany-rgb-reverse-white-web-footer.png

249 ms

iconmonstr-twitter-3-icon-256.png

iconmonstr-twitter-3-icon-256.png

268 ms

iconmonstr-linkedin-3-icon-256.png

iconmonstr-linkedin-3-icon-256.png

286 ms

to-top-icon.png

to-top-icon.png

307 ms

ScriptResource.axd

ScriptResource.axd

34 ms

mag-icon-sm.png

mag-icon-sm.png

142 ms

2206 ms

sfPublicContent.gif

sfPublicContent.gif

138 ms

footer-search-icon.png

footer-search-icon.png

139 ms

translateelement.css

translateelement.css

22 ms

main.js

main.js

134 ms

analytics.js

analytics.js

35 ms

element_main.js

element_main.js

39 ms

collect

collect

12 ms

translate_24dp.png

translate_24dp.png

35 ms

l

l

120 ms

googlelogo_color_42x16dp.png

googlelogo_color_42x16dp.png

32 ms

bootstrap.min.css

bootstrap.min.css

272 ms

animate.css

animate.css

262 ms

icomoon.css

icomoon.css

265 ms

talispoint.css

talispoint.css

276 ms

pmsi_ext_3.css

pmsi_ext_3.css

257 ms

jquery.1.9.1.min.js

jquery.1.9.1.min.js

343 ms

jquery.placeholder.js

jquery.placeholder.js

406 ms

talispoint.js

talispoint.js

498 ms

talispoint_rules.js

talispoint_rules.js

413 ms

radius_density.js

radius_density.js

413 ms

pmsi.js

pmsi.js

414 ms

pmsi_google.js

pmsi_google.js

491 ms

bootstrap.min.js

bootstrap.min.js

559 ms

bootstrap-hover-dropdown.min.js

bootstrap-hover-dropdown.min.js

566 ms

ga.js

ga.js

4 ms

__utm.gif

__utm.gif

11 ms

pmsi_walgreens.jpg

pmsi_walgreens.jpg

192 ms

RadiusSearchIcon.png

RadiusSearchIcon.png

165 ms

PharmaLookupIcon.png

PharmaLookupIcon.png

151 ms

RegionSearchIcon.png

RegionSearchIcon.png

161 ms

DownloadIcon.png

DownloadIcon.png

164 ms

EmailIcon.png

EmailIcon.png

154 ms

TextMessageIcon.png

TextMessageIcon.png

307 ms

Accessibility Review

tmesys.com accessibility score

97

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

<frame> or <iframe> elements do not have a title

Best Practices

tmesys.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tmesys.com SEO score

71

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

Links are not crawlable

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tmesys.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tmesys.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

tmesys.com

Open Graph description is not detected on the main page of Tmesys. 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: