Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

gilead.com

Gilead Sciences, Inc.

Page Load Speed

1.3 sec in total

First Response

104 ms

Resources Loaded

1 sec

Page Rendered

212 ms

gilead.com screenshot

About Website

Visit gilead.com now to see the best up-to-date Gilead content for United States and also check out these interesting facts you probably never knew about gilead.com

Gilead Sciences, Inc. is a research-based biopharmaceutical company focused on the discovery, development, and commercialization of innovative medicines.

Visit gilead.com

Key Findings

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

Performance Metrics

gilead.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value9,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

gilead.com

104 ms

html5.js

22 ms

styles

57 ms

auto

54 ms

frameworks

55 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 32% of them (22 requests) were addressed to the original Gilead.com, 34% (23 requests) were made to Use.typekit.net and 4% (3 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (368 ms) belongs to the original domain Gilead.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 537.9 kB (68%)

Content Size

795.5 kB

After Optimization

257.7 kB

In fact, the total size of Gilead.com main page is 795.5 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. 60% of websites need less resources to load. Images take 479.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 100.4 kB

  • Original 112.0 kB
  • After minification 91.5 kB
  • After compression 11.6 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 20.6 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 100.4 kB or 90% of the original size.

Image Optimization

-60%

Potential reduce by 289.8 kB

  • Original 479.5 kB
  • After minification 189.6 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, Gilead needs image optimization as it can save up to 289.8 kB or 60% 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 147.6 kB

  • Original 204.0 kB
  • After minification 204.0 kB
  • After compression 56.4 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 147.6 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (57%)

Requests Now

44

After Optimization

19

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

Accessibility Review

gilead.com accessibility score

89

Accessibility Issues

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-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gilead.com SEO score

92

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

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 Gilead.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 Gilead.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 Gilead. 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: