Tools & Wizards About Us
oraje.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

oraje.com

HOME | Oraje..

Page Load Speed

2 sec in total

First Response

621 ms

Resources Loaded

1.2 sec

Page Rendered

230 ms

oraje.com screenshot

About Website

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

Visit oraje.com

Key Findings

We analyzed Oraje.com page load time and found that the first response time was 621 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

oraje.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

www.oraje.com

621 ms

minified.js

78 ms

focus-within-polyfill.js

132 ms

polyfill.min.js

24 ms

bootstrap-features.1a4c9633.chunk.min.js

176 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Oraje.com, 82% (36 requests) were made to Static.parastorage.com and 7% (3 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (621 ms) belongs to the original domain Oraje.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.4 kB (68%)

Content Size

402.9 kB

After Optimization

129.5 kB

  • HTML
  • JavaScript

In fact, the total size of Oraje.com main page is 402.9 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. 65% of websites need less resources to load. HTML takes 335.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 259.0 kB

  • Original 335.8 kB
  • After minification 334.1 kB
  • After compression 76.8 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 259.0 kB or 77% of the original size.

JavaScript Optimization

-21%

Potential reduce by 14.4 kB

  • Original 67.1 kB
  • After minification 65.8 kB
  • After compression 52.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 14.4 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (88%)

Requests Now

42

After Optimization

5

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

www.oraje.com

www.oraje.com

621 ms

minified.js

minified.js

78 ms

focus-within-polyfill.js

focus-within-polyfill.js

132 ms

polyfill.min.js

polyfill.min.js

24 ms

bootstrap-features.1a4c9633.chunk.min.js

bootstrap-features.1a4c9633.chunk.min.js

176 ms

main.3cf6985e.chunk.min.js

main.3cf6985e.chunk.min.js

186 ms

lodash.min.js

lodash.min.js

185 ms

wix-code-sdk-providers.abe00d40.chunk.min.js

wix-code-sdk-providers.abe00d40.chunk.min.js

187 ms

ooi.193ebd59.chunk.min.js

ooi.193ebd59.chunk.min.js

189 ms

siteMembers.e334253a.chunk.min.js

siteMembers.e334253a.chunk.min.js

186 ms

siteScrollBlocker.9d56bfbb.chunk.min.js

siteScrollBlocker.9d56bfbb.chunk.min.js

187 ms

tpaCommons.cfa00117.chunk.min.js

tpaCommons.cfa00117.chunk.min.js

189 ms

windowMessageRegistrar.10a60538.chunk.min.js

windowMessageRegistrar.10a60538.chunk.min.js

283 ms

platform.0d806ad4.chunk.min.js

platform.0d806ad4.chunk.min.js

284 ms

vendors~vendor-react-dom.f5baf244.chunk.min.js

vendors~vendor-react-dom.f5baf244.chunk.min.js

284 ms

vendor-react-dom.5a11925f.chunk.min.js

vendor-react-dom.5a11925f.chunk.min.js

283 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

282 ms

bolt-performance

bolt-performance

299 ms

dynamicmodel

dynamicmodel

199 ms

clientWorker.a116b36b.bundle.min.js

clientWorker.a116b36b.bundle.min.js

281 ms

bt

bt

273 ms

bundle.min.js

bundle.min.js

272 ms

custom-elements-polyfill.1214d81c.chunk.min.js

custom-elements-polyfill.1214d81c.chunk.min.js

166 ms

intersection-observer-polyfill.2d33ae31.chunk.min.js

intersection-observer-polyfill.2d33ae31.chunk.min.js

121 ms

thunderboltElements.1c45958a.bundle.min.js

thunderboltElements.1c45958a.bundle.min.js

123 ms

wix-perf-measure.bundle.min.js

wix-perf-measure.bundle.min.js

123 ms

activePopup.a4f4f37b.chunk.min.js

activePopup.a4f4f37b.chunk.min.js

109 ms

dropdownMenu.b4d795c3.chunk.min.js

dropdownMenu.b4d795c3.chunk.min.js

120 ms

navigation.3534bd58.chunk.min.js

navigation.3534bd58.chunk.min.js

132 ms

ooiTpaSharedConfig.5b026f10.chunk.min.js

ooiTpaSharedConfig.5b026f10.chunk.min.js

132 ms

pageScroll.1d0d396e.chunk.min.js

pageScroll.1d0d396e.chunk.min.js

135 ms

platformPubsub.4e2ca26d.chunk.min.js

platformPubsub.4e2ca26d.chunk.min.js

135 ms

scrollRestoration.d3b24f96.chunk.min.js

scrollRestoration.d3b24f96.chunk.min.js

135 ms

scrollToAnchor.bcfb16ba.chunk.min.js

scrollToAnchor.bcfb16ba.chunk.min.js

135 ms

tpa.e67d2d12.chunk.min.js

tpa.e67d2d12.chunk.min.js

134 ms

windowScroll.21a40acb.chunk.min.js

windowScroll.21a40acb.chunk.min.js

162 ms

screenIn.8890a0d0.chunk.min.js

screenIn.8890a0d0.chunk.min.js

161 ms

bootstrap-components.3c327a15.chunk.min.js

bootstrap-components.3c327a15.chunk.min.js

160 ms

DropDownMenu_PointerMenuButtonSkin.5d1116c2.chunk.min.js

DropDownMenu_PointerMenuButtonSkin.5d1116c2.chunk.min.js

161 ms

PinnedLayer.4080072e.chunk.min.js

PinnedLayer.4080072e.chunk.min.js

160 ms

tpa-components.60e72493.chunk.min.js

tpa-components.60e72493.chunk.min.js

238 ms

bt

bt

50 ms

lodash.min.js

lodash.min.js

40 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

52 ms

Accessibility Review

oraje.com accessibility score

100

Accessibility Issues

Best Practices

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

oraje.com SEO score

93

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

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

oraje.com

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