Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

stage.fei.com

Thermo Fisher Scientific | High-performance Electron Microscopy Workflow Solutions

Page Load Speed

9.6 sec in total

First Response

3.7 sec

Resources Loaded

5.6 sec

Page Rendered

209 ms

stage.fei.com screenshot

About Website

Welcome to stage.fei.com homepage info - get ready to check Stage Fei best content for United States right away, or after learning these important things about stage.fei.com

Thermo Fisher Scientific's innovative microscopy and application expertise helps customers find meaningful answers to questions that accelerate breakthrough discoveries, increase productivity, and ult...

Visit stage.fei.com

Key Findings

We analyzed Stage.fei.com page load time and found that the first response time was 3.7 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

stage.fei.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

stage.fei.com

3733 ms

ektron.stylesheet.ashx

272 ms

ektron.javascript.ashx

451 ms

jquery-2.1.0.min.js

22 ms

jquery-migrate-1.2.1.min.js

22 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 69% of them (76 requests) were addressed to the original Stage.fei.com, 7% (8 requests) were made to Google-analytics.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Stage.fei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.3 kB (18%)

Content Size

1.4 MB

After Optimization

1.2 MB

In fact, the total size of Stage.fei.com main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 40.6 kB

  • Original 55.8 kB
  • After minification 51.1 kB
  • After compression 15.2 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 40.6 kB or 73% of the original size.

Image Optimization

-15%

Potential reduce by 172.5 kB

  • Original 1.2 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. Obviously, Stage Fei needs image optimization as it can save up to 172.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 20.8 kB

  • Original 142.2 kB
  • After minification 142.1 kB
  • After compression 121.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 20.8 kB or 15% of the original size.

CSS Optimization

-39%

Potential reduce by 20.3 kB

  • Original 52.1 kB
  • After minification 52.1 kB
  • After compression 31.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. Stage.fei.com needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (61%)

Requests Now

103

After Optimization

40

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

Accessibility Review

stage.fei.com accessibility score

79

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

stage.fei.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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stage.fei.com SEO score

67

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stage.fei.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Stage.fei.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 Stage Fei. 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: