Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

4.2 sec in total

First Response

202 ms

Resources Loaded

3.7 sec

Page Rendered

297 ms

ortigo.com screenshot

About Website

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

Ortigo Online Auctions. Buy, sell cars, urban clothing, fashion apparel, electronics, collectibles, sporting goods, digital cameras, wheels, baby items, everything else on the best online auction webs...

Visit ortigo.com

Key Findings

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

Performance Metrics

ortigo.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

ortigo.com

202 ms

www.ortigo.com

1251 ms

global.css

125 ms

JsHttpRequest.js

154 ms

jsencode.js

148 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 92% of them (108 requests) were addressed to the original Ortigo.com, 3% (3 requests) were made to S7.addthis.com and 3% (3 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ortigo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 654.1 kB (60%)

Content Size

1.1 MB

After Optimization

427.4 kB

In fact, the total size of Ortigo.com main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 685.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 142.4 kB

  • Original 169.8 kB
  • After minification 146.6 kB
  • After compression 27.4 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. This page needs HTML code to be minified as it can gain 23.2 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 142.4 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 15.7 kB

  • Original 190.5 kB
  • After minification 174.8 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. Ortigo images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 465.1 kB

  • Original 685.3 kB
  • After minification 618.1 kB
  • After compression 220.2 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 465.1 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 30.9 kB

  • Original 36.0 kB
  • After minification 25.2 kB
  • After compression 5.0 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. Ortigo.com needs all CSS files to be minified and compressed as it can save up to 30.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (51%)

Requests Now

113

After Optimization

55

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

Accessibility Review

ortigo.com accessibility score

86

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

ortigo.com best practices score

92

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

Page has valid source maps

SEO Factors

ortigo.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ortigo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ortigo.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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