Tools & Wizards About Us
invega.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

invega.com

INVEGA® for the Treatment of Schizophrenia & Schizoaffective Disorder

Page Load Speed

3.7 sec in total

First Response

79 ms

Resources Loaded

3.3 sec

Page Rendered

321 ms

invega.com screenshot

About Website

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

Visit invega.com

Key Findings

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

Performance Metrics

invega.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.399

25/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

invega.com

79 ms

52 ms

www.invega.com

1571 ms

css_50126087a9040f1aee8bfe85f78813c3.css

80 ms

js_5b8ec905d82f8e3c6d35063505b4a740.js

110 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 91% of them (32 requests) were addressed to the original Invega.com, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Invega.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.4 kB (16%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 31.4 kB

  • Original 40.3 kB
  • After minification 38.9 kB
  • After compression 9.0 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 31.4 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 97.1 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. INVEGA images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-69%

Potential reduce by 33.0 kB

  • Original 48.1 kB
  • After minification 45.8 kB
  • After compression 15.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. Invega.com needs all CSS files to be minified and compressed as it can save up to 33.0 kB or 69% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

32

After Optimization

32

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INVEGA. According to our analytics all requests are already optimized.

Network Requests Diagram

invega.com

invega.com

79 ms

52 ms

www.invega.com

www.invega.com

1571 ms

css_50126087a9040f1aee8bfe85f78813c3.css

css_50126087a9040f1aee8bfe85f78813c3.css

80 ms

js_5b8ec905d82f8e3c6d35063505b4a740.js

js_5b8ec905d82f8e3c6d35063505b4a740.js

110 ms

bg.png

bg.png

1328 ms

analytics.js

analytics.js

1289 ms

gtm.js

gtm.js

1289 ms

bg-footer.png

bg-footer.png

26 ms

sp-general-icons.png

sp-general-icons.png

29 ms

logo.png

logo.png

28 ms

bg-menu.png

bg-menu.png

32 ms

sp-main-menu.png

sp-main-menu.png

66 ms

list-image-sub-menu.gif

list-image-sub-menu.gif

26 ms

content-bg.gif

content-bg.gif

34 ms

slider-bg.png

slider-bg.png

48 ms

comming-soon-pill-reminder.png

comming-soon-pill-reminder.png

87 ms

slider-img-understading.png

slider-img-understading.png

105 ms

slider-learn-more.png

slider-learn-more.png

55 ms

slider-img-schizophrenia-treatment.png

slider-img-schizophrenia-treatment.png

137 ms

slider-img-15daysfree.png

slider-img-15daysfree.png

193 ms

slider-img-invega-approved.png

slider-img-invega-approved.png

134 ms

callout-home-bg.png

callout-home-bg.png

133 ms

sp-callout-home.png

sp-callout-home.png

151 ms

janssen-consumer-logo-white.png

janssen-consumer-logo-white.png

130 ms

janssen-prescription-assistance-badge-gray.png

janssen-prescription-assistance-badge-gray.png

152 ms

shadow.png

shadow.png

210 ms

background-external-link.png

background-external-link.png

170 ms

bg-overlay-homepage.png

bg-overlay-homepage.png

195 ms

btn-external-link-close.png

btn-external-link-close.png

183 ms

title-callout-overlay.gif

title-callout-overlay.gif

216 ms

bg-callout-overlay.png

bg-callout-overlay.png

231 ms

sp-overlay-callout-img.png

sp-overlay-callout-img.png

233 ms

collect

collect

11 ms

css_9d1da35abcbcec4911c10216944754ad.css

css_9d1da35abcbcec4911c10216944754ad.css

25 ms

Accessibility Review

invega.com accessibility score

100

Accessibility Issues

Best Practices

invega.com best practices score

67

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

SEO Factors

invega.com SEO score

58

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

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 Invega.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 Invega.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

invega.com

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