Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

okor.com

Custom TradeStation EasyLanguage,NinjaTrader Programmer,Expert Witness Code Comparison

Page Load Speed

806 ms in total

First Response

140 ms

Resources Loaded

553 ms

Page Rendered

113 ms

okor.com screenshot

About Website

Visit okor.com now to see the best up-to-date Okor content and also check out these interesting facts you probably never knew about okor.com

Programmer and Expert Witness, Stuart Okorofsky is an expert TradeStation and NinjaTrader programmer who programs trading systems, indicators, and user functions for stocks and futures traders in the ...

Visit okor.com

Key Findings

We analyzed Okor.com page load time and found that the first response time was 140 ms and then it took 666 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

okor.com performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

okor.com

140 ms

js

66 ms

style.css

57 ms

CSScriptLib.js

106 ms

mainGraphic.jpg

158 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 88% of them (7 requests) were addressed to the original Okor.com, 13% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (357 ms) belongs to the original domain Okor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.5 kB (22%)

Content Size

331.8 kB

After Optimization

257.3 kB

In fact, the total size of Okor.com main page is 331.8 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 5% of websites need less resources to load. Images take 322.4 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 5.7 kB

  • Original 8.8 kB
  • After minification 7.8 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.0 kB, which is 12% 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 5.7 kB or 65% of the original size.

Image Optimization

-21%

Potential reduce by 68.7 kB

  • Original 322.4 kB
  • After minification 253.7 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. Obviously, Okor needs image optimization as it can save up to 68.7 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-16%

Potential reduce by 92 B

  • Original 582 B
  • After minification 582 B
  • After compression 490 B

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. Okor.com needs all CSS files to be minified and compressed as it can save up to 92 B or 16% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Okor. According to our analytics all requests are already optimized.

Accessibility Review

okor.com accessibility score

57

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

okor.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • 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 Okor.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 Okor.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 Okor. 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: