Tools & Wizards About Us
aspenoss.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

aspenoss.com

Aspen API. More than just an API. Your personal API partner.

Page Load Speed

2.6 sec in total

First Response

89 ms

Resources Loaded

1.9 sec

Page Rendered

644 ms

aspenoss.com screenshot

About Website

Welcome to aspenoss.com homepage info - get ready to check Aspen Oss best content right away, or after learning these important things about aspenoss.com

With quality, compliance and collaboration being part of our DNA, we continuously strive to improve and provide the ultimate solution.

Visit aspenoss.com

Key Findings

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

Performance Metrics

aspenoss.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

aspenoss.com

89 ms

www.aspenapi.com

1412 ms

mmenu.css

4 ms

icons.css

31 ms

all.css

26 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Aspenoss.com, 70% (43 requests) were made to Aspenapi.com and 20% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Aspenapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.3 kB (7%)

Content Size

3.8 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 46.6 kB

  • Original 58.3 kB
  • After minification 54.7 kB
  • After compression 11.7 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 46.6 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 127.9 kB

  • Original 3.5 MB
  • After minification 3.4 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. Aspen Oss images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 94.5 kB

  • Original 138.2 kB
  • After minification 138.2 kB
  • After compression 43.7 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 94.5 kB or 68% of the original size.

CSS Optimization

-18%

Potential reduce by 14.3 kB

  • Original 78.2 kB
  • After minification 78.2 kB
  • After compression 63.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. Aspenoss.com needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (33%)

Requests Now

40

After Optimization

27

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aspen Oss. 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 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

aspenoss.com

aspenoss.com

89 ms

www.aspenapi.com

www.aspenapi.com

1412 ms

mmenu.css

mmenu.css

4 ms

icons.css

icons.css

31 ms

all.css

all.css

26 ms

uc.js

uc.js

49 ms

style.min.css

style.min.css

34 ms

main.css

main.css

23 ms

style.css

style.css

23 ms

huibert.css

huibert.css

32 ms

js

js

71 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

38 ms

mmenu.js

mmenu.js

35 ms

jparticle.jquery.js

jparticle.jquery.js

35 ms

main.js

main.js

35 ms

css2

css2

33 ms

css2

css2

44 ms

login.svg

login.svg

28 ms

logo.svg

logo.svg

6 ms

banner-bg.jpg

banner-bg.jpg

14 ms

ecovadis-logo.png

ecovadis-logo.png

15 ms

cphi-logo-rgb-milan-colour.png

cphi-logo-rgb-milan-colour.png

7 ms

AAPS-PharmSci-360.png

AAPS-PharmSci-360.png

11 ms

tides-europe.png

tides-europe.png

7 ms

texture1.png

texture1.png

9 ms

development_solution_icon.svg

development_solution_icon.svg

12 ms

texture2.png

texture2.png

13 ms

established_api_portfolio_icon.svg

established_api_portfolio_icon.svg

16 ms

texture3.png

texture3.png

18 ms

service_support_icon.svg

service_support_icon.svg

17 ms

Nieke-linkedin-992x518.png

Nieke-linkedin-992x518.png

32 ms

Ecovadis-website-2-992x558.png

Ecovadis-website-2-992x558.png

20 ms

PMDA-logo-992x499.png

PMDA-logo-992x499.png

19 ms

who-we-are-concept.jpg

who-we-are-concept.jpg

26 ms

2020-CO-SRU-LR-1.jpg

2020-CO-SRU-LR-1.jpg

34 ms

2020-C0-BB-LR-6.jpg

2020-C0-BB-LR-6.jpg

31 ms

2020-CO-MOLENEIND-FHFPFF-LR-1.jpg

2020-CO-MOLENEIND-FHFPFF-LR-1.jpg

35 ms

2020-CO-WAREHOUSE-WEEGKAMER-2.jpg

2020-CO-WAREHOUSE-WEEGKAMER-2.jpg

57 ms

flexible-capacity-batch-size.svg

flexible-capacity-batch-size.svg

32 ms

map.jpg

map.jpg

47 ms

aspen-oss-logo-dia-footer.svg

aspen-oss-logo-dia-footer.svg

43 ms

fcc-logo-dia-footer.svg

fcc-logo-dia-footer.svg

44 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

34 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

50 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

57 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

66 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

67 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

55 ms

fa-brands-400.ttf

fa-brands-400.ttf

20 ms

HelveticaNeue-Italic.woff

HelveticaNeue-Italic.woff

19 ms

HelveticaNeue.woff

HelveticaNeue.woff

19 ms

HelveticaNeue-Medium.woff

HelveticaNeue-Medium.woff

19 ms

HelveticaNeue-Light.woff

HelveticaNeue-Light.woff

18 ms

HelveticaNeue-Bold.woff

HelveticaNeue-Bold.woff

20 ms

icomoon.ttf

icomoon.ttf

20 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsovBJ.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsovBJ.ttf

54 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ.ttf

52 ms

Accessibility Review

aspenoss.com accessibility score

68

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aspenoss.com SEO score

97

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aspenoss.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 Aspenoss.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

aspenoss.com

Open Graph data is detected on the main page of Aspen Oss. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: