Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

tripos.com

Certara | Accelerating Medicines with Biosimulation and Tech-enabled Services

Page Load Speed

1.8 sec in total

First Response

103 ms

Resources Loaded

1.4 sec

Page Rendered

239 ms

About Website

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

The global leader in accelerating medicines with biosimulation. Since 2014, our customers, who use our software and tech-enabled services, have received 90% of new drug approvals by the FDA.

Visit tripos.com

Key Findings

We analyzed Tripos.com page load time and found that the first response time was 103 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

tripos.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value2,830 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.361

30/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

tripos.com

103 ms

www.certara.com

594 ms

qcb2hhd.js

183 ms

select2.min.css

18 ms

A.screen.css.pagespeed.cf.XfVE47DByi.css

132 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tripos.com, 55% (35 requests) were made to Certara.com and 25% (16 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (691 ms) relates to the external source Js.hubspot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 562.9 kB (36%)

Content Size

1.6 MB

After Optimization

988.0 kB

In fact, the total size of Tripos.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. 60% of websites need less resources to load. Images take 830.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 33.6 kB

  • Original 43.9 kB
  • After minification 43.9 kB
  • After compression 10.3 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 33.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 910 B

  • Original 830.9 kB
  • After minification 830.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. Tripos images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 132.8 kB

  • Original 215.4 kB
  • After minification 213.1 kB
  • After compression 82.6 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 132.8 kB or 62% of the original size.

CSS Optimization

-86%

Potential reduce by 395.5 kB

  • Original 460.6 kB
  • After minification 459.3 kB
  • After compression 65.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. Tripos.com needs all CSS files to be minified and compressed as it can save up to 395.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (45%)

Requests Now

47

After Optimization

26

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

Accessibility Review

tripos.com accessibility score

89

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.

ARIA

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.

Impact

Issue

High

ARIA IDs are not unique

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

Links do not have a discernible name

Best Practices

tripos.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

tripos.com SEO score

86

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tripos.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 Tripos.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

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