Tools & Wizards About Us
tms.org screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

tms.org

TMS | The Minerals, Metals & Materials Society

Page Load Speed

2.7 sec in total

First Response

138 ms

Resources Loaded

2.2 sec

Page Rendered

304 ms

tms.org screenshot

About Website

Click here to check amazing TMS content for United States. Otherwise, check out these important facts you probably never knew about tms.org

TMS is the home society for minerals, metals and materials scientists and engineers worldwide. Explore membership, publications, PD and more.

Visit tms.org

Key Findings

We analyzed Tms.org page load time and found that the first response time was 138 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

tms.org performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.338

33/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

tms.org

138 ms

TMSHome.aspx

695 ms

allscripts.js

140 ms

swfobject_modified.js

297 ms

style.css

116 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 81% of them (48 requests) were addressed to the original Tms.org, 5% (3 requests) were made to Tms.informz.net and 5% (3 requests) were made to Materialstechnology.tms.org. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Tms.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 482.1 kB (29%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tms.org main page is 1.7 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 120.0 kB

  • Original 162.3 kB
  • After minification 148.4 kB
  • After compression 42.2 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 120.0 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 64.5 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. TMS images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 292.4 kB

  • Original 413.4 kB
  • After minification 368.7 kB
  • After compression 121.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 292.4 kB or 71% of the original size.

CSS Optimization

-76%

Potential reduce by 5.1 kB

  • Original 6.7 kB
  • After minification 5.1 kB
  • After compression 1.6 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. Tms.org needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (33%)

Requests Now

55

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tms.org

tms.org

138 ms

TMSHome.aspx

TMSHome.aspx

695 ms

allscripts.js

allscripts.js

140 ms

swfobject_modified.js

swfobject_modified.js

297 ms

style.css

style.css

116 ms

WebResource.axd

WebResource.axd

231 ms

WebResource.axd

WebResource.axd

385 ms

ScriptResource.axd

ScriptResource.axd

388 ms

ScriptResource.axd

ScriptResource.axd

413 ms

ga.js

ga.js

30 ms

sp.js

sp.js

161 ms

LinkedIN.gif

LinkedIN.gif

146 ms

FaceBook.gif

FaceBook.gif

155 ms

Flickr.gif

Flickr.gif

252 ms

Youtube.gif

Youtube.gif

249 ms

icon-Email.gif

icon-Email.gif

316 ms

socialTwitter18x18.jpg

socialTwitter18x18.jpg

337 ms

SocialSitesBtn.gif

SocialSitesBtn.gif

335 ms

WebResource.axd

WebResource.axd

326 ms

WhiteArrow.gif

WhiteArrow.gif

371 ms

WebResource.axd

WebResource.axd

406 ms

WebResource.axd

WebResource.axd

407 ms

__utm.gif

__utm.gif

31 ms

55 ms

brand

brand

35 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

747 ms

jq-slidey.js

jq-slidey.js

254 ms

style.css

style.css

220 ms

jquery.countdown.css

jquery.countdown.css

255 ms

jquery.countdown.js

jquery.countdown.js

296 ms

COMIC-tanium_TMSHomepage-Skyscraper2.png

COMIC-tanium_TMSHomepage-Skyscraper2.png

465 ms

LakeShore_TMSJOM_140x250_MicroMag_final.jpg

LakeShore_TMSJOM_140x250_MicroMag_final.jpg

457 ms

TMS2016_LateReg_Slider_tmsorg.png

TMS2016_LateReg_Slider_tmsorg.png

536 ms

SilentAuction_tmsorg_Slider.png

SilentAuction_tmsorg_Slider.png

904 ms

MST16_Slider.png

MST16_Slider.png

1445 ms

Molten16-Reg-Slider-tmsorg.png

Molten16-Reg-Slider-tmsorg.png

1243 ms

3DMS-Reg_slider.png

3DMS-Reg_slider.png

992 ms

tabNewsSelected.jpg

tabNewsSelected.jpg

695 ms

tabMyMeetingsOff.jpg

tabMyMeetingsOff.jpg

1254 ms

brand

brand

58 ms

DMMM2.JPG

DMMM2.JPG

451 ms

PSFE.jpg

PSFE.jpg

422 ms

2016-spotlight-feb.jpg

2016-spotlight-feb.jpg

439 ms

tabMyProfileOff.jpg

tabMyProfileOff.jpg

853 ms

jomCurrentCover.gif

jomCurrentCover.gif

940 ms

rigaku_feb_web.gif

rigaku_feb_web.gif

951 ms

2016IMABanner150x200.jpg

2016IMABanner150x200.jpg

1025 ms

shimadzu_dec.gif

shimadzu_dec.gif

1021 ms

2013-ELA-On-Demand-Banner_200x150.jpg

2013-ELA-On-Demand-Banner_200x150.jpg

1068 ms

dot.gif

dot.gif

13 ms

grey-bar-gradient.jpg

grey-bar-gradient.jpg

574 ms

tms.org-header_main.jpg

tms.org-header_main.jpg

980 ms

grey-bar-gradient.jpg

grey-bar-gradient.jpg

992 ms

Sidebar-box-header140x18.gif

Sidebar-box-header140x18.gif

355 ms

grey-table-gradient150-700.jpg

grey-table-gradient150-700.jpg

379 ms

btn_off.gif

btn_off.gif

373 ms

marketplace.png

marketplace.png

578 ms

tms.org_footer.jpg

tms.org_footer.jpg

541 ms

btn_marker.png

btn_marker.png

379 ms

Accessibility Review

tms.org accessibility score

84

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

tms.org best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

tms.org SEO score

91

Search Engine Optimization Advices

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tms.org 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 Tms.org main page’s claimed encoding is . 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

tms.org

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