Tools & Wizards About Us
orteo.pl screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

orteo.pl

Sklep medyczny: sprzęt rehabilitacyjny, ortopedyczny

Page Load Speed

2.9 sec in total

First Response

267 ms

Resources Loaded

2.5 sec

Page Rendered

188 ms

orteo.pl screenshot

About Website

Welcome to orteo.pl homepage info - get ready to check Orteo best content for Poland right away, or after learning these important things about orteo.pl

Orteo.pl to specjalistyczny sklep medyczny dla seniorów i osób niepełnosprawnych ☑️ W ofercie sprzęt rehabilitacyjny i ortopedyczny dla dorosłych i dzieci.

Visit orteo.pl

Key Findings

We analyzed Orteo.pl page load time and found that the first response time was 267 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

orteo.pl performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value3,960 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.385

27/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

orteo.pl

267 ms

www.orteo.pl

865 ms

gtm.js

98 ms

js

199 ms

styles.min_1717744020.css

245 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 32% of them (11 requests) were addressed to the original Orteo.pl, 12% (4 requests) were made to Google.com and 12% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (869 ms) belongs to the original domain Orteo.pl.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Orteo.pl main page is 1.4 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. 50% of websites need less resources to load. Images take 683.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 54.2 kB

  • Original 74.7 kB
  • After minification 65.7 kB
  • After compression 20.5 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 9.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 54.2 kB or 73% of the original size.

Image Optimization

-10%

Potential reduce by 68.3 kB

  • Original 683.7 kB
  • After minification 615.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. Orteo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 557.0 kB
  • After minification 557.0 kB
  • After compression 555.8 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

-0%

Potential reduce by 235 B

  • Original 78.5 kB
  • After minification 78.5 kB
  • After compression 78.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. Orteo.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (73%)

Requests Now

30

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

orteo.pl

orteo.pl

267 ms

www.orteo.pl

www.orteo.pl

865 ms

gtm.js

gtm.js

98 ms

js

js

199 ms

styles.min_1717744020.css

styles.min_1717744020.css

245 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

449 ms

links.pol.1_1718085374.min.js

links.pol.1_1718085374.min.js

357 ms

scripts.min_1669119700.js

scripts.min_1669119700.js

869 ms

api.js

api.js

42 ms

conversion.js

conversion.js

113 ms

0529a7f9-cec6-461d-a340-bb6ea5ecce45

0529a7f9-cec6-461d-a340-bb6ea5ecce45

631 ms

api6.ipify.org

api6.ipify.org

13 ms

platform.js

platform.js

30 ms

orteo_black190_1.png

orteo_black190_1.png

118 ms

icon-cart-dark.png

icon-cart-dark.png

110 ms

1138x400_pictures_Projekt_bez_tytulu_4.png

1138x400_pictures_Projekt_bez_tytulu_4.png

859 ms

adframe

adframe

246 ms

analytics.js

analytics.js

57 ms

107 ms

fbevents.js

fbevents.js

114 ms

edrone_2_0.js

edrone_2_0.js

112 ms

machinelearningtracker

machinelearningtracker

287 ms

bat.js

bat.js

145 ms

recaptcha__en.js

recaptcha__en.js

145 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

43 ms

ec.js

ec.js

55 ms

badge

badge

116 ms

collect

collect

104 ms

collect

collect

118 ms

102 ms

1007973029281152

1007973029281152

67 ms

no_rating.png

no_rating.png

18 ms

ga-audiences

ga-audiences

66 ms

collect

collect

19 ms

Accessibility Review

orteo.pl accessibility score

78

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

<frame> or <iframe> elements do not have a title

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

orteo.pl best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

orteo.pl SEO score

93

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

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

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

orteo.pl

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