Tools & Wizards About Us
lne.pl screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lne.pl

LNE - Profesjonalny magazyn kosmetyczny Beauty & Healthy Aging

Page Load Speed

7.3 sec in total

First Response

872 ms

Resources Loaded

5.9 sec

Page Rendered

492 ms

lne.pl screenshot

About Website

Click here to check amazing LNE content for Poland. Otherwise, check out these important facts you probably never knew about lne.pl

LNE to nr 1 w branży beauty i healthy aging. To profesjonalny magazyn kosmetyczny, ukazujący się w Polsce od 1995 roku. Wiodące działy to: kosmetologia w praktyce, pielęgnacja, healthy aging, medical ...

Visit lne.pl

Key Findings

We analyzed Lne.pl page load time and found that the first response time was 872 ms and then it took 6.4 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

lne.pl performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.2 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,410 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

lne.pl

872 ms

js

79 ms

js

103 ms

gtm.js

103 ms

font-awesome.min.css

238 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 38% of them (40 requests) were addressed to the original Lne.pl, 22% (23 requests) were made to Cdn.exposupport.pl and 10% (10 requests) were made to Revive.lne.pl. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Cdn.exposupport.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 413.3 kB (29%)

Content Size

1.4 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 34.6 kB

  • Original 44.9 kB
  • After minification 42.7 kB
  • After compression 10.3 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 34.6 kB or 77% of the original size.

Image Optimization

-32%

Potential reduce by 69.0 kB

  • Original 218.6 kB
  • After minification 149.6 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. Obviously, LNE needs image optimization as it can save up to 69.0 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 309.2 kB

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

CSS Optimization

-30%

Potential reduce by 495 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.2 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. Lne.pl needs all CSS files to be minified and compressed as it can save up to 495 B or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (67%)

Requests Now

94

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lne.pl

lne.pl

872 ms

js

js

79 ms

js

js

103 ms

gtm.js

gtm.js

103 ms

font-awesome.min.css

font-awesome.min.css

238 ms

brands.css

brands.css

900 ms

solid.css

solid.css

1527 ms

flag-icon.min.css

flag-icon.min.css

1637 ms

bootstrap.css

bootstrap.css

1752 ms

kendo.common.min.css

kendo.common.min.css

1875 ms

kendo.bootstrap.min.css

kendo.bootstrap.min.css

1655 ms

ngDialog.min.css

ngDialog.min.css

1643 ms

ngDialog-theme-default.css

ngDialog-theme-default.css

1635 ms

ngDialog-ajs.css

ngDialog-ajs.css

1642 ms

modules.css

modules.css

1643 ms

ajs-form.css

ajs-form.css

1748 ms

ajs-base.css

ajs-base.css

1639 ms

codemirror.css

codemirror.css

1759 ms

show-hint.css

show-hint.css

1756 ms

CSSHandlerV2.ashx

CSSHandlerV2.ashx

1862 ms

css

css

50 ms

head_logo.png

head_logo.png

1636 ms

head_logo_white.png

head_logo_white.png

1642 ms

lightbox.css

lightbox.css

1742 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

1989 ms

bootstrap.js

bootstrap.js

1755 ms

angular.min.js

angular.min.js

2091 ms

angular-sanitize.min.js

angular-sanitize.min.js

1760 ms

angular-messages.min.js

angular-messages.min.js

1853 ms

angular-cookies.min.js

angular-cookies.min.js

1864 ms

ngDialog.min.js

ngDialog.min.js

1922 ms

codemirror.js

codemirror.js

2320 ms

css.js

css.js

1973 ms

show-hint.js

show-hint.js

2004 ms

ui-codemirror.js

ui-codemirror.js

2004 ms

kendo.all.min.js

kendo.all.min.js

3684 ms

kendo.culture.pl.min.js

kendo.culture.pl.min.js

2080 ms

helper.js

helper.js

2121 ms

exs.module.js

exs.module.js

1754 ms

common.js

common.js

2121 ms

require.js

require.js

2193 ms

lightbox.min.js

lightbox.min.js

1853 ms

asyncjs.php

asyncjs.php

714 ms

countdown.js

countdown.js

239 ms

js

js

91 ms

pfr.png

pfr.png

1972 ms

js

js

172 ms

analytics.js

analytics.js

377 ms

js

js

146 ms

uc.js

uc.js

295 ms

landing

landing

285 ms

js

js

126 ms

js

js

273 ms

destination

destination

271 ms

collect

collect

250 ms

LNE154.png

LNE154.png

1497 ms

154-na-tropie-zrodel-tradziku.jpg

154-na-tropie-zrodel-tradziku.jpg

1499 ms

154-w-labiryncie-trychologii.jpg

154-w-labiryncie-trychologii.jpg

1637 ms

154-zloto-dla-zuchwalych.jpg

154-zloto-dla-zuchwalych.jpg

1637 ms

all-articles-back.png

all-articles-back.png

1596 ms

najlepsze-skladniki-w-pielegnacji-stop.jpg

najlepsze-skladniki-w-pielegnacji-stop.jpg

1603 ms

hydro-revital-terapia-environ.jpg

hydro-revital-terapia-environ.jpg

1841 ms

kluczowa-substancja-w-holistycznej-kosmetologii.jpg

kluczowa-substancja-w-holistycznej-kosmetologii.jpg

1842 ms

byebye-tradzik.png

byebye-tradzik.png

1824 ms

46-kongres.png

46-kongres.png

1831 ms

Beauty-innovations-2023-4-5-grudnia-online.jpg

Beauty-innovations-2023-4-5-grudnia-online.jpg

1942 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1931 ms

collect

collect

47 ms

ga-audiences

ga-audiences

93 ms

last_magazin_button.png

last_magazin_button.png

769 ms

img-default.jpg

img-default.jpg

776 ms

close.png

close.png

791 ms

loading.gif

loading.gif

792 ms

prev.png

prev.png

881 ms

next.png

next.png

888 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

19 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

28 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff

36 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXx-p7K4GLs.woff

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXx-p7K4GLs.woff

50 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXx-p7K4GLs.woff

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXx-p7K4GLs.woff

48 ms

countdown_api.js

countdown_api.js

92 ms

fbevents.js

fbevents.js

96 ms

asyncspc.php

asyncspc.php

235 ms

ArticleViewV1.js

ArticleViewV1.js

135 ms

ConditionalRedirectV1.js

ConditionalRedirectV1.js

134 ms

ArticleViewAsPopupV1.js

ArticleViewAsPopupV1.js

134 ms

MenuV1.js

MenuV1.js

131 ms

72 ms

flip.css

flip.css

81 ms

flipdown.js

flipdown.js

82 ms

jssocials.min.js

jssocials.min.js

121 ms

wawa-counter.jpg

wawa-counter.jpg

574 ms

js.js

js.js

16 ms

0ac43d4c045b9e01e442391adafc0fd9.png

0ac43d4c045b9e01e442391adafc0fd9.png

242 ms

lg.php

lg.php

374 ms

dd0da366c84a1d70f8a632efb7cca9e3.png

dd0da366c84a1d70f8a632efb7cca9e3.png

482 ms

lg.php

lg.php

428 ms

139b290c6790bdf8a0a7d3afffd7c447.png

139b290c6790bdf8a0a7d3afffd7c447.png

602 ms

lg.php

lg.php

426 ms

5781a69c02138ed7bc61de234bbff9fa.jpg

5781a69c02138ed7bc61de234bbff9fa.jpg

603 ms

lg.php

lg.php

504 ms

Accessibility Review

lne.pl accessibility score

90

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

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

lne.pl 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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

lne.pl

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