Tools & Wizards About Us
inles.si screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

inles.si

Inles d.d. - Okna, vrata, panoramske stene, senčila

Page Load Speed

6.6 sec in total

First Response

644 ms

Resources Loaded

5.5 sec

Page Rendered

451 ms

inles.si screenshot

About Website

Visit inles.si now to see the best up-to-date Inles content and also check out these interesting facts you probably never knew about inles.si

Inles d.d. je proizvajalec stavbnega pohištva. Ponujamo vam lesena okna, les-alu okna, pvc okna, vhodna vrata, lesena vrata, pvc vrata, panoramske stene itd.

Visit inles.si

Key Findings

We analyzed Inles.si page load time and found that the first response time was 644 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

inles.si performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value27.8 s

0/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.466

19/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

inles.si

644 ms

js

79 ms

twemoji.js

249 ms

wp-emoji.js

330 ms

css

36 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 85% of them (100 requests) were addressed to the original Inles.si, 4% (5 requests) were made to Fonts.googleapis.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Inles.si.

Page Optimization Overview & Recommendations

Page size can be reduced by 392.0 kB (9%)

Content Size

4.5 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inles.si main page is 4.5 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. 65% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 156.0 kB

  • Original 196.9 kB
  • After minification 187.1 kB
  • After compression 40.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 156.0 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 133.9 kB

  • Original 3.2 MB
  • After minification 3.1 MB

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. Inles images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 97.0 kB

  • Original 905.1 kB
  • After minification 904.9 kB
  • After compression 808.1 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 97.0 kB or 11% of the original size.

CSS Optimization

-3%

Potential reduce by 5.1 kB

  • Original 180.9 kB
  • After minification 180.9 kB
  • After compression 175.8 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. Inles.si has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 93 (82%)

Requests Now

113

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inles.si

inles.si

644 ms

js

js

79 ms

twemoji.js

twemoji.js

249 ms

wp-emoji.js

wp-emoji.js

330 ms

css

css

36 ms

kzbt.css

kzbt.css

492 ms

kzbt.css

kzbt.css

608 ms

jquery-ui.css

jquery-ui.css

26 ms

kzbt.css

kzbt.css

374 ms

css

css

52 ms

kzbt.css

kzbt.css

495 ms

js

js

97 ms

analytics.js

analytics.js

42 ms

kzbt.css

kzbt.css

510 ms

css

css

30 ms

css

css

58 ms

kzbt.css

kzbt.css

337 ms

kzbt.js

kzbt.js

744 ms

kzbt.js

kzbt.js

458 ms

kzbt.js

kzbt.js

500 ms

kzbt.js

kzbt.js

622 ms

kzbt.js

kzbt.js

582 ms

all.css

all.css

73 ms

printThis.min.js

printThis.min.js

52 ms

css

css

52 ms

kzbt.css

kzbt.css

610 ms

index.js

index.js

614 ms

index.js

index.js

623 ms

scripts.js

scripts.js

697 ms

email-subscribers-public.js

email-subscribers-public.js

727 ms

accordion.js

accordion.js

731 ms

menu.js

menu.js

736 ms

regenerator-runtime.js

regenerator-runtime.js

851 ms

wp-polyfill.js

wp-polyfill.js

852 ms

dom-ready.js

dom-ready.js

853 ms

hooks.js

hooks.js

853 ms

i18n.js

i18n.js

916 ms

a11y.js

a11y.js

917 ms

autocomplete.js

autocomplete.js

916 ms

controlgroup.js

controlgroup.js

938 ms

checkboxradio.js

checkboxradio.js

964 ms

button.js

button.js

982 ms

datepicker.js

datepicker.js

985 ms

mouse.js

mouse.js

983 ms

resizable.js

resizable.js

985 ms

draggable.js

draggable.js

1056 ms

dialog.js

dialog.js

1080 ms

api.js

api.js

123 ms

droppable.js

droppable.js

1080 ms

collect

collect

23 ms

selectmenu.js

selectmenu.js

962 ms

progressbar.js

progressbar.js

886 ms

selectable.js

selectable.js

840 ms

slider.js

slider.js

851 ms

spinner.js

spinner.js

827 ms

sortable.js

sortable.js

825 ms

tabs.js

tabs.js

760 ms

tooltip.js

tooltip.js

724 ms

effect.js

effect.js

726 ms

effect-blind.js

effect-blind.js

760 ms

effect-bounce.js

effect-bounce.js

746 ms

effect-clip.js

effect-clip.js

717 ms

effect-drop.js

effect-drop.js

719 ms

effect-explode.js

effect-explode.js

718 ms

effect-fade.js

effect-fade.js

717 ms

effect-fold.js

effect-fold.js

722 ms

effect-highlight.js

effect-highlight.js

714 ms

effect-pulsate.js

effect-pulsate.js

713 ms

effect-size.js

effect-size.js

714 ms

collect

collect

54 ms

effect-scale.js

effect-scale.js

602 ms

effect-shake.js

effect-shake.js

604 ms

effect-slide.js

effect-slide.js

683 ms

effect-transfer.js

effect-transfer.js

705 ms

rbtools.min.js

rbtools.min.js

767 ms

rs6.min.js

rs6.min.js

783 ms

bootstrap.js

bootstrap.js

655 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

47 ms

uwpqsfscript.js

uwpqsfscript.js

656 ms

fa-solid-900.woff

fa-solid-900.woff

22 ms

fa-regular-400.woff

fa-regular-400.woff

65 ms

plugins.js

plugins.js

838 ms

menu.js

menu.js

695 ms

animations.min.js

animations.min.js

713 ms

jplayer.min.js

jplayer.min.js

721 ms

translate3d.js

translate3d.js

808 ms

scripts.js

scripts.js

786 ms

scripts.js

scripts.js

754 ms

index.js

index.js

726 ms

front.min.js

front.min.js

727 ms

posts_messenger.js

posts_messenger.js

805 ms

mfn-icons.woff

mfn-icons.woff

977 ms

inles-75-let.jpg

inles-75-let.jpg

1057 ms

england-flag.jpg

england-flag.jpg

765 ms

germany-flag.jpg

germany-flag.jpg

743 ms

prodajna-akcija-april-julij-24-1-1.jpg

prodajna-akcija-april-julij-24-1-1.jpg

1076 ms

house-architecture-photography-hd-wallpaper-1920x1200-9237.jpg

house-architecture-photography-hd-wallpaper-1920x1200-9237.jpg

1505 ms

interior_design-wallpaper-1280x800.jpg

interior_design-wallpaper-1280x800.jpg

1067 ms

architecture-design-modern-house-pool.jpg

architecture-design-modern-house-pool.jpg

1456 ms

eko-sklad-1366x600.jpg

eko-sklad-1366x600.jpg

970 ms

30911662_l.jpg

30911662_l.jpg

1185 ms

slika-alu-vrata.jpg

slika-alu-vrata.jpg

1180 ms

polkna-sencila.jpg

polkna-sencila.jpg

1071 ms

prodajna-akcija-april-julij-24-1-960x480.jpg

prodajna-akcija-april-julij-24-1-960x480.jpg

1070 ms

sejem-Dom-24-popust-1-960x480.jpg

sejem-Dom-24-popust-1-960x480.jpg

1184 ms

knjiga.png

knjiga.png

1106 ms

eko-sklad.png

eko-sklad.png

1184 ms

izracun.png

izracun.png

1182 ms

vrata.png

vrata.png

1191 ms

sertifikat.png

sertifikat.png

1190 ms

pasivna-gradnja.png

pasivna-gradnja.png

1288 ms

fb.png

fb.png

1209 ms

tw.png

tw.png

1199 ms

spinner.gif

spinner.gif

1187 ms

fancy_heading_hr.png

fancy_heading_hr.png

1223 ms

NAGIBNEhomepage-1.jpg

NAGIBNEhomepage-1.jpg

2331 ms

recaptcha__en.js

recaptcha__en.js

26 ms

admin-ajax.php

admin-ajax.php

1620 ms

Accessibility Review

inles.si accessibility score

80

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

inles.si best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

inles.si SEO score

90

Search Engine Optimization Advices

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

    SL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inles.si can be misinterpreted by Google and other search engines. Our service has detected that Slovenian is used on the page, and it does not match the claimed English language. Our system also found out that Inles.si 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

inles.si

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