Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 92

    SEO

    Google-friendlier than
    79% of websites

triny.pl

TRINY.pl - kosmetyki naturalne i organiczne, zdrowa żywność

Page Load Speed

10.6 sec in total

First Response

1.4 sec

Resources Loaded

9 sec

Page Rendered

206 ms

triny.pl screenshot

About Website

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

Naturalne kosmetyki z polskich manufaktur i całego świata. Zdrowa żywność, superfoods. Opinie klientów, niskie ceny i ekspresowa wysyłka!

Visit triny.pl

Key Findings

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

Performance Metrics

triny.pl performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.435

21/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

triny.pl

1378 ms

131e012bd3d120cfee3c0291302bb7df_all.css

933 ms

customer-s1.css

281 ms

a74d84a66912e88da58b21c4e1544da2.js

1292 ms

conversion.js

14 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 9% of them (7 requests) were addressed to the original Triny.pl, 18% (14 requests) were made to S2.triny.pl and 16% (12 requests) were made to S1.triny.pl. The less responsive or slowest element that took the longest time to load (5.9 sec) relates to the external source S3.triny.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 807.9 kB (36%)

Content Size

2.2 MB

After Optimization

1.4 MB

In fact, the total size of Triny.pl main page is 2.2 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 82.2 kB

  • Original 100.0 kB
  • After minification 99.9 kB
  • After compression 17.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 82.2 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 28.0 kB

  • Original 1.2 MB
  • After minification 1.2 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. TRINY images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 452.1 kB

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

CSS Optimization

-84%

Potential reduce by 245.6 kB

  • Original 292.5 kB
  • After minification 287.3 kB
  • After compression 46.9 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. Triny.pl needs all CSS files to be minified and compressed as it can save up to 245.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (28%)

Requests Now

72

After Optimization

52

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRINY. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

triny.pl accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

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

High

Page has valid source maps

SEO Factors

triny.pl SEO score

92

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

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

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

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