Tools & Wizards About Us
oleant.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

oleant.com

Bespoke Design Luminaires | Oleant Lighting | Budapest

Page Load Speed

3 sec in total

First Response

153 ms

Resources Loaded

2.8 sec

Page Rendered

65 ms

oleant.com screenshot

About Website

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

We specialize in elegant efficient indoor LED lighting for home, office, and commercial use. Choose from our range of bespoke design luminaires, ready-made products or request custom designs.

Visit oleant.com

Key Findings

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

oleant.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

www.oleant.com

153 ms

minified.js

37 ms

focus-within-polyfill.js

35 ms

polyfill.min.js

1026 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

62 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Oleant.com, 37% (22 requests) were made to Static.parastorage.com and 25% (15 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (58%)

Content Size

2.0 MB

After Optimization

834.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Oleant.com main page is 2.0 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. 60% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 936.1 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 206.9 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 936.1 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 2.2 kB

  • Original 344.6 kB
  • After minification 342.4 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. Oleant images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 228.8 kB

  • Original 514.5 kB
  • After minification 514.5 kB
  • After compression 285.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 228.8 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (34%)

Requests Now

35

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.oleant.com

www.oleant.com

153 ms

minified.js

minified.js

37 ms

focus-within-polyfill.js

focus-within-polyfill.js

35 ms

polyfill.min.js

polyfill.min.js

1026 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

thunderbolt-commons.c1d8ed1c.bundle.min.js

62 ms

main.4a2d1e74.bundle.min.js

main.4a2d1e74.bundle.min.js

69 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

63 ms

lodash.min.js

lodash.min.js

68 ms

react.production.min.js

react.production.min.js

70 ms

react-dom.production.min.js

react-dom.production.min.js

68 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

64 ms

core.js

core.js

110 ms

white_drop_shadow_slr.png

white_drop_shadow_slr.png

350 ms

5f0e8d_a7dc78c87804487f96e4aa4e91167644~mv2.jpg

5f0e8d_a7dc78c87804487f96e4aa4e91167644~mv2.jpg

491 ms

5f0e8d_6420edb973954868a433a534e32496e7~mv2.jpg

5f0e8d_6420edb973954868a433a534e32496e7~mv2.jpg

508 ms

portrait_pbd.jpg

portrait_pbd.jpg

565 ms

5f0e8d_734c4a64cd0d40a9b7d715ddbd758427f000.jpg

5f0e8d_734c4a64cd0d40a9b7d715ddbd758427f000.jpg

549 ms

5f0e8d_e3c0360c1aca414b9ad138b759ac5408~mv2.jpg

5f0e8d_e3c0360c1aca414b9ad138b759ac5408~mv2.jpg

554 ms

5f0e8d_fcebc6d3efb74a3c94da10a6edb738ee~mv2.png

5f0e8d_fcebc6d3efb74a3c94da10a6edb738ee~mv2.png

588 ms

5f0e8d_139a3465fa98479f8930e3b571f6734e~mv2.jpg

5f0e8d_139a3465fa98479f8930e3b571f6734e~mv2.jpg

629 ms

5f0e8d_5b807446c34c4565b69aa963d913dc2c~mv2.jpg

5f0e8d_5b807446c34c4565b69aa963d913dc2c~mv2.jpg

659 ms

5f0e8d_9a20de5b2e6c4decb3017fa992bf8238~mv2.jpg

5f0e8d_9a20de5b2e6c4decb3017fa992bf8238~mv2.jpg

813 ms

5f0e8d_ec1ca0b13f34442bbd79c9e184932df7~mv2.jpg

5f0e8d_ec1ca0b13f34442bbd79c9e184932df7~mv2.jpg

714 ms

5f0e8d_38f81b03df0a418ebf8b81c146910768~mv2.jpg

5f0e8d_38f81b03df0a418ebf8b81c146910768~mv2.jpg

761 ms

5f0e8d_dfa13c269c244ae09fd54c88ae89067c~mv2.jpg

5f0e8d_dfa13c269c244ae09fd54c88ae89067c~mv2.jpg

894 ms

5f0e8d_d6c367e610e7408a970c619e4b40188a~mv2.jpg

5f0e8d_d6c367e610e7408a970c619e4b40188a~mv2.jpg

953 ms

final.png

final.png

871 ms

zuqx3k1yUEl3Eavo-ZPEAhX141arjC0UgpdoDjjeeVk.woff

zuqx3k1yUEl3Eavo-ZPEAhX141arjC0UgpdoDjjeeVk.woff

65 ms

zuqx3k1yUEl3Eavo-ZPEAhNmD6bOwmI0fiYv_Ehe03s.woff

zuqx3k1yUEl3Eavo-ZPEAhNmD6bOwmI0fiYv_Ehe03s.woff

64 ms

iEjm9hVxcattz37Y8gZwVebEnH4R5m1MLXJyCi0BC78.woff

iEjm9hVxcattz37Y8gZwVebEnH4R5m1MLXJyCi0BC78.woff

65 ms

iEjm9hVxcattz37Y8gZwVergGQquJ_f3dxTxEJk8ZKM.woff

iEjm9hVxcattz37Y8gZwVergGQquJ_f3dxTxEJk8ZKM.woff

65 ms

cormorant-garamond-v7-latin-ext_latin_cyrillic-700italic.woff

cormorant-garamond-v7-latin-ext_latin_cyrillic-700italic.woff

67 ms

cormorant-garamond-v7-latin-ext_latin_cyrillic-italic.woff

cormorant-garamond-v7-latin-ext_latin_cyrillic-italic.woff

65 ms

cormorant-garamond-v7-latin-ext_latin_cyrillic-700.woff

cormorant-garamond-v7-latin-ext_latin_cyrillic-700.woff

66 ms

cormorant-garamond-v7-latin-ext_latin_cyrillic-regular.woff

cormorant-garamond-v7-latin-ext_latin_cyrillic-regular.woff

67 ms

bundle.min.js

bundle.min.js

115 ms

main.97c41ef3.js

main.97c41ef3.js

63 ms

WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff

WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff

71 ms

STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff

STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff

70 ms

163 ms

163 ms

160 ms

157 ms

153 ms

154 ms

192 ms

190 ms

189 ms

185 ms

182 ms

184 ms

223 ms

84 ms

80 ms

ct.html

ct.html

11 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

23 ms

deprecation-style.v5.css

deprecation-style.v5.css

9 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

oleant.com accessibility score

96

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.

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

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

oleant.com SEO score

99

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

    EN

  • Encoding

    UTF-8

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

oleant.com

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