Tools & Wizards About Us
htseq.princeton.edu screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

htseq.princeton.edu

Princeton University High Throughput Sequencing Database

Page Load Speed

808 ms in total

First Response

114 ms

Resources Loaded

616 ms

Page Rendered

78 ms

htseq.princeton.edu screenshot

About Website

Welcome to htseq.princeton.edu homepage info - get ready to check Htseq Princeton best content for United States right away, or after learning these important things about htseq.princeton.edu

HTSEQ, the Princeton University High Throughput Sequencing Database, stores raw and processed data from high throughput sequencing assays. It provides data retrieval and analysis interfaces. Data is r...

Visit htseq.princeton.edu

Key Findings

We analyzed Htseq.princeton.edu page load time and found that the first response time was 114 ms and then it took 694 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

htseq.princeton.edu performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

htseq.princeton.edu

114 ms

htseq.princeton.edu

465 ms

style-body-production.css

22 ms

style-main-all.css

30 ms

jquery-ui-1.8.2.custom.css

29 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 280.9 kB (72%)

Content Size

390.3 kB

After Optimization

109.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Htseq.princeton.edu main page is 390.3 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 307.0 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 6.5 kB

  • Original 9.8 kB
  • After minification 8.9 kB
  • After compression 3.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 6.5 kB or 67% of the original size.

Image Optimization

-7%

Potential reduce by 649 B

  • Original 8.8 kB
  • After minification 8.1 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. Htseq Princeton images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 219.6 kB

  • Original 307.0 kB
  • After minification 305.3 kB
  • After compression 87.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 219.6 kB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 54.1 kB

  • Original 64.8 kB
  • After minification 47.8 kB
  • After compression 10.7 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. Htseq.princeton.edu needs all CSS files to be minified and compressed as it can save up to 54.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (56%)

Requests Now

16

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

htseq.princeton.edu

htseq.princeton.edu

114 ms

htseq.princeton.edu

htseq.princeton.edu

465 ms

style-body-production.css

style-body-production.css

22 ms

style-main-all.css

style-main-all.css

30 ms

jquery-ui-1.8.2.custom.css

jquery-ui-1.8.2.custom.css

29 ms

superfish.css

superfish.css

22 ms

jquery.js

jquery.js

40 ms

jquery-ui-1.8.21.custom.min.js

jquery-ui-1.8.21.custom.min.js

48 ms

jquery_ui_init.js

jquery_ui_init.js

27 ms

image_dialog.js

image_dialog.js

32 ms

hoverIntent.js

hoverIntent.js

33 ms

superfish.js

superfish.js

34 ms

logo.jpg

logo.jpg

7 ms

ui-bg_highlight-hard_15_66ff66_1x100.png

ui-bg_highlight-hard_15_66ff66_1x100.png

6 ms

arrows-ffffff.png

arrows-ffffff.png

7 ms

shadow.png

shadow.png

7 ms

ui-bg_highlight-hard_100_f5f3e5_1x100.png

ui-bg_highlight-hard_100_f5f3e5_1x100.png

8 ms

style-main-all-print.css

style-main-all-print.css

6 ms

Accessibility Review

htseq.princeton.edu accessibility score

95

Accessibility Issues

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

htseq.princeton.edu 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

htseq.princeton.edu SEO score

77

Search Engine Optimization Advices

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 Htseq.princeton.edu 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 Htseq.princeton.edu 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

htseq.princeton.edu

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