Tools & Wizards About Us
alchem.pl screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

alchem.pl

Sprzęt laboratoryjny | Odczynniki — Sklep chemiczny Alchem

Page Load Speed

5.1 sec in total

First Response

985 ms

Resources Loaded

3.6 sec

Page Rendered

503 ms

alchem.pl screenshot

About Website

Welcome to alchem.pl homepage info - get ready to check Alchem best content right away, or after learning these important things about alchem.pl

Kompleksowe wyposażenie laboratorium. Ponad 700 000 produktów. Polskie i światowe marki. Projektowanie laboratoriów pod klucz. Doświadczony serwis.

Visit alchem.pl

Key Findings

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

Performance Metrics

alchem.pl performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.794

5/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

www.alchem.eu

985 ms

core.js

234 ms

jquery-ui-1.8.17.custom.css

356 ms

style.css

359 ms

jquery.js

42 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Alchem.pl, 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Alchem.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 817.0 kB (14%)

Content Size

6.0 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 39.1 kB

  • Original 47.7 kB
  • After minification 46.7 kB
  • After compression 8.6 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 39.1 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 461.8 kB

  • Original 5.5 MB
  • After minification 5.0 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. Alchem images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 261.6 kB

  • Original 334.7 kB
  • After minification 280.2 kB
  • After compression 73.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 261.6 kB or 78% of the original size.

CSS Optimization

-86%

Potential reduce by 54.6 kB

  • Original 63.4 kB
  • After minification 47.5 kB
  • After compression 8.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. Alchem.pl needs all CSS files to be minified and compressed as it can save up to 54.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (15%)

Requests Now

40

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.alchem.eu

www.alchem.eu

985 ms

core.js

core.js

234 ms

jquery-ui-1.8.17.custom.css

jquery-ui-1.8.17.custom.css

356 ms

style.css

style.css

359 ms

jquery.js

jquery.js

42 ms

jquery.imagemapster.js

jquery.imagemapster.js

592 ms

mapy.js

mapy.js

384 ms

alchem.js

alchem.js

241 ms

jquery.maskedinput-1.3.min.js

jquery.maskedinput-1.3.min.js

349 ms

jquery-ui-1.8.17.min.js

jquery-ui-1.8.17.min.js

835 ms

bg.png

bg.png

168 ms

white.png

white.png

168 ms

Arctiko%20logo.jpg

Arctiko%20logo.jpg

949 ms

red.png

red.png

169 ms

strzalka-left.png

strzalka-left.png

170 ms

strzalka-right.png

strzalka-right.png

171 ms

mtargi.jpg

mtargi.jpg

239 ms

komora013%20640x640%202.jpg

komora013%20640x640%202.jpg

594 ms

podz.zdj.bmp

podz.zdj.bmp

597 ms

border-bottom.png

border-bottom.png

247 ms

alchem.png

alchem.png

248 ms

1065653-shopping_cart.jpg

1065653-shopping_cart.jpg

483 ms

2.jpg

2.jpg

729 ms

istock_000017672547_extrasmall%202.jpg

istock_000017672547_extrasmall%202.jpg

488 ms

4.jpg

4.jpg

849 ms

istock_000017803415_extrasmall%202.jpg

istock_000017803415_extrasmall%202.jpg

732 ms

benchmark%20logo.jpg

benchmark%20logo.jpg

961 ms

simax%20logo2.jpg

simax%20logo2.jpg

717 ms

sa%20logo%20red.jpg

sa%20logo%20red.jpg

1202 ms

aldrich%20chemistry%20red%202%202.jpg

aldrich%20chemistry%20red%202%202.jpg

1348 ms

fluka%20analytical%20red%202%202.jpg

fluka%20analytical%20red%202%202.jpg

1122 ms

sigma_lifescience%202%202.jpg

sigma_lifescience%202%202.jpg

1450 ms

supelco_analytical%202%202.jpg

supelco_analytical%202%202.jpg

1315 ms

dr.weigert_400x52.jpg

dr.weigert_400x52.jpg

1093 ms

binder%20logo%204c.jpg

binder%20logo%204c.jpg

1483 ms

search.png

search.png

1240 ms

search-input.png

search-input.png

1319 ms

icon1.png

icon1.png

1361 ms

icon3.png

icon3.png

1434 ms

gazela2011.jpg

gazela2011.jpg

1436 ms

avalon-webfont.woff

avalon-webfont.woff

1446 ms

footer-red.png

footer-red.png

1321 ms

Accessibility Review

alchem.pl accessibility score

73

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

[role]s do not have all required [aria-*] attributes

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Page has valid source maps

SEO Factors

alchem.pl SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

alchem.pl

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