Tools & Wizards About Us
rotis-lj.si screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

rotis-lj.si

ROTIS Home page - ROTIS

Page Load Speed

4.2 sec in total

First Response

605 ms

Resources Loaded

3 sec

Page Rendered

581 ms

rotis-lj.si screenshot

About Website

Welcome to rotis-lj.si homepage info - get ready to check ROTIS Lj best content right away, or after learning these important things about rotis-lj.si

We manufacture all types of slewing bearings based on technical specifications obtained as well as numerous Rotis slewing bearings of a standard type.

Visit rotis-lj.si

Key Findings

We analyzed Rotis-lj.si page load time and found that the first response time was 605 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

rotis-lj.si performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

605 ms

css

34 ms

js

71 ms

h5zlz.css

99 ms

h5zlz.css

198 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 76% of them (53 requests) were addressed to the original Rotis-lj.si, 14% (10 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (813 ms) belongs to the original domain Rotis-lj.si.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.3 kB (2%)

Content Size

4.5 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rotis-lj.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. 70% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 67.2 kB

  • Original 83.6 kB
  • After minification 80.7 kB
  • After compression 16.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. 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 67.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 30.4 kB

  • Original 4.0 MB
  • After minification 3.9 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. ROTIS Lj images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.8 kB

  • Original 453.0 kB
  • After minification 453.0 kB
  • After compression 447.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 1.9 kB

  • Original 34.2 kB
  • After minification 34.1 kB
  • After compression 32.3 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. Rotis-lj.si has all CSS files already compressed.

Requests Breakdown

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

Requests Now

57

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

605 ms

css

css

34 ms

js

js

71 ms

h5zlz.css

h5zlz.css

99 ms

h5zlz.css

h5zlz.css

198 ms

h5zlz.css

h5zlz.css

297 ms

h5zlz.css

h5zlz.css

295 ms

h5zlz.css

h5zlz.css

300 ms

h5zlz.css

h5zlz.css

296 ms

h5zlz.css

h5zlz.css

312 ms

h5zlz.css

h5zlz.css

313 ms

h5zlz.css

h5zlz.css

395 ms

h5zlz.js

h5zlz.js

394 ms

h5zlz.js

h5zlz.js

591 ms

h5zlz.js

h5zlz.js

400 ms

h5zlz.css

h5zlz.css

411 ms

index.js

index.js

410 ms

index.js

index.js

493 ms

avia.js

avia.js

662 ms

shortcodes.js

shortcodes.js

663 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

508 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

664 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

662 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

662 ms

comment-reply.min.js

comment-reply.min.js

692 ms

api.js

api.js

55 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

693 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

692 ms

wp-polyfill.min.js

wp-polyfill.min.js

702 ms

index.js

index.js

726 ms

akismet-frontend.js

akismet-frontend.js

726 ms

brave.js

brave.js

812 ms

css

css

19 ms

sidebarv2.js

sidebarv2.js

88 ms

header-bg.jpg

header-bg.jpg

201 ms

logo.png

logo.png

198 ms

intro-image.jpg

intro-image.jpg

371 ms

TbmLezaj.png

TbmLezaj.png

409 ms

StrokovnoSvetoavnje.jpg

StrokovnoSvetoavnje.jpg

607 ms

sample-slide-1-2.png

sample-slide-1-2.png

661 ms

strojni-deli-partial-bg.jpg

strojni-deli-partial-bg.jpg

468 ms

Zobnik.png

Zobnik.png

566 ms

Zvarjenec.png

Zvarjenec.png

567 ms

StrojDel.png

StrojDel.png

508 ms

Rotis_production_capacities_1.jpg

Rotis_production_capacities_1.jpg

664 ms

Rotis_prodcution_capacities_4.jpg

Rotis_prodcution_capacities_4.jpg

708 ms

Rotis_production_capacities_3.jpg

Rotis_production_capacities_3.jpg

667 ms

Rotis_production_capacities_2.jpg

Rotis_production_capacities_2.jpg

666 ms

cta-bg-1.png

cta-bg-1.png

704 ms

footer-map.jpg

footer-map.jpg

760 ms

logo-footer.png

logo-footer.png

761 ms

Boniteta-V-En-300x300.png

Boniteta-V-En-300x300.png

765 ms

logo-optiweb.png

logo-optiweb.png

766 ms

preloader.png

preloader.png

803 ms

icon-checkbox.png

icon-checkbox.png

763 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

58 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

64 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

86 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

86 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

97 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

87 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

75 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

75 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

102 ms

icomoon.ttf

icomoon.ttf

809 ms

footer-bg.jpg

footer-bg.jpg

813 ms

embed.js

embed.js

190 ms

K2FufZ1EmftJSV9VQpXb1lo9vC3nZWuiyvUxGI4.ttf

K2FufZ1EmftJSV9VQpXb1lo9vC3nZWuiyvUxGI4.ttf

73 ms

recaptcha__en.js

recaptcha__en.js

59 ms

h5zlz.css

h5zlz.css

100 ms

Accessibility Review

rotis-lj.si accessibility score

74

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

rotis-lj.si best practices score

83

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

Page has valid source maps

SEO Factors

rotis-lj.si 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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

rotis-lj.si

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