Tools & Wizards About Us
abbvie.bugtrack.net screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

abbvie.bugtrack.net

Login - BUGtrack

Page Load Speed

894 ms in total

First Response

52 ms

Resources Loaded

713 ms

Page Rendered

129 ms

abbvie.bugtrack.net screenshot

About Website

Visit abbvie.bugtrack.net now to see the best up-to-date Abbvie BUGtrack content for Canada and also check out these interesting facts you probably never knew about abbvie.bugtrack.net

Visit abbvie.bugtrack.net

Key Findings

We analyzed Abbvie.bugtrack.net page load time and found that the first response time was 52 ms and then it took 842 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

abbvie.bugtrack.net performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

abbvie.bugtrack.net

52 ms

abbvie.bugtrack.net

166 ms

stat

167 ms

login.aspx

33 ms

modernizr-2.7.1.min.js

25 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Abbvie.bugtrack.net and no external sources were called. The less responsive or slowest element that took the longest time to load (199 ms) belongs to the original domain Abbvie.bugtrack.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.0 kB (69%)

Content Size

508.8 kB

After Optimization

159.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Abbvie.bugtrack.net main page is 508.8 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. Only 10% of websites need less resources to load. Javascripts take 463.2 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 2.1 kB

  • Original 3.6 kB
  • After minification 3.6 kB
  • After compression 1.5 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 2.1 kB or 59% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.5 kB
  • After minification 4.5 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. Abbvie BUGtrack images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 318.3 kB

  • Original 463.2 kB
  • After minification 463.0 kB
  • After compression 144.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 318.3 kB or 69% of the original size.

CSS Optimization

-76%

Potential reduce by 28.6 kB

  • Original 37.5 kB
  • After minification 37.3 kB
  • After compression 8.9 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. Abbvie.bugtrack.net needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (60%)

Requests Now

10

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

abbvie.bugtrack.net

abbvie.bugtrack.net

52 ms

abbvie.bugtrack.net

abbvie.bugtrack.net

166 ms

stat

stat

167 ms

login.aspx

login.aspx

33 ms

modernizr-2.7.1.min.js

modernizr-2.7.1.min.js

25 ms

facade.min.css

facade.min.css

47 ms

jquery-1.12.0.min.js

jquery-1.12.0.min.js

161 ms

jquery-ui-1.11.4.min.js

jquery-ui-1.11.4.min.js

199 ms

knockout-3.4.0.min.js

knockout-3.4.0.min.js

136 ms

fscorlib.min.js

fscorlib.min.js

110 ms

i18n.ashx

i18n.ashx

70 ms

bugtrack.min.css

bugtrack.min.css

65 ms

bugtrack.min.js

bugtrack.min.js

87 ms

logo.jpg

logo.jpg

35 ms

Accessibility Review

abbvie.bugtrack.net accessibility score

66

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

abbvie.bugtrack.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

abbvie.bugtrack.net SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Abbvie.bugtrack.net 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 Abbvie.bugtrack.net 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

abbvie.bugtrack.net

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