Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

orijen.com

ORIJEN | Premium Pet Food for Dogs & Cats

Page Load Speed

3 sec in total

First Response

134 ms

Resources Loaded

2.3 sec

Page Rendered

584 ms

orijen.com screenshot

About Website

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

Orijen is the pinnacle of nature’s nourishment with protein-rich, Wholeprey diets so your pet can thrive. Find the best dog & cat food for your pet today!

Visit orijen.com

Key Findings

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

Performance Metrics

orijen.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value4,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value27.1 s

0/100

10%

Network Requests Diagram

orijen.com

134 ms

homepage

143 ms

ps-widget.js

129 ms

api.js

78 ms

bv.js

66 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Orijen.com, 34% (43 requests) were made to Orijenpetfoods.com and 10% (13 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (987 ms) relates to the external source Orijenpetfoods.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.6 kB (21%)

Content Size

1.6 MB

After Optimization

1.2 MB

In fact, the total size of Orijen.com main page is 1.6 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. Only a small number of websites need less resources to load. Javascripts take 690.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 299.1 kB

  • Original 394.2 kB
  • After minification 392.6 kB
  • After compression 95.1 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 299.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 349.6 kB
  • After minification 349.6 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. ORIJEN images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 31.4 kB

  • Original 690.1 kB
  • After minification 689.9 kB
  • After compression 658.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.1 kB

  • Original 133.7 kB
  • After minification 133.7 kB
  • After compression 132.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. Orijen.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

103

After Optimization

41

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

Accessibility Review

orijen.com accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role] values are not valid

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

orijen.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

orijen.com SEO score

76

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

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 Orijen.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 Orijen.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 ORIJEN. 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: