3.1 sec in total
411 ms
2.5 sec
209 ms
Welcome to roze.pl homepage info - get ready to check Roze best content right away, or after learning these important things about roze.pl
Szukasz kwiaciarni? Wyjątkowe, piękne i świeże kwiaty, bukiety i kompozycje z dostawą w Warszawie. Darmowa dostawa kwiatów Warszawa. Zapraszamy 7 dni w tygodniu!
Visit roze.plWe analyzed Roze.pl page load time and found that the first response time was 411 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.
roze.pl performance score
name
value
score
weighting
Value2.1 s
79/100
10%
Value5.0 s
26/100
25%
Value3.5 s
88/100
10%
Value800 ms
36/100
30%
Value0.008
100/100
15%
Value3.5 s
92/100
10%
411 ms
579 ms
333 ms
223 ms
4 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Roze.pl, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (936 ms) belongs to the original domain Roze.pl.
Page size can be reduced by 29.0 kB (34%)
85.2 kB
56.1 kB
In fact, the total size of Roze.pl main page is 85.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 42.9 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.8 kB or 77% of the original size.
Potential reduce by 23 B
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. Roze images are well optimized though.
Potential reduce by 2.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 2.1 kB or 25% of the original size.
Potential reduce by 16.1 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. Roze.pl needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 82% of the original size.
Number of requests can be reduced by 25 (52%)
48
23
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
roze.pl
411 ms
579 ms
main.css
333 ms
popups.js
223 ms
urchin.js
4 ms
background.gif
113 ms
top.jpg
356 ms
logo.gif
244 ms
menu2.gif
244 ms
blueCorners_topleft.gif
234 ms
blueCorners_topright.gif
256 ms
blueCorners_right.gif
239 ms
blueArrow.gif
349 ms
blueCorners_bottomleft.gif
357 ms
blueCorners_bottomright.gif
352 ms
grayCorners_topleft.gif
354 ms
grayCorners_topright.gif
370 ms
grayCorners_right.gif
464 ms
grayArrow.gif
463 ms
grayCorners_bottomleft.gif
464 ms
grayCorners_bottomright.gif
464 ms
honeyCorners_topleft.gif
474 ms
honeyCorners_topright.gif
486 ms
honeyCorners_right.gif
573 ms
zmien_walute.gif
577 ms
honeyCorners_bottomleft.gif
574 ms
honeyCorners_bottomright.gif
574 ms
przelewy24_rodzaje.gif
715 ms
gray2Corners_topleft.gif
715 ms
gray2Corners_topright.gif
683 ms
gray2Corners_right.gif
683 ms
S010_small.jpg
684 ms
kup_teraz.gif
692 ms
opis.gif
793 ms
gray2Corners_bottomleft.gif
794 ms
gray2Corners_bottomright.gif
797 ms
S015_small.jpg
936 ms
S002_small.jpg
843 ms
S012_small.jpg
829 ms
topNews.gif
904 ms
__utm.gif
2 ms
pic5.jpg
886 ms
redArrow.gif
806 ms
bottomNews.gif
721 ms
brownCorners_topleft.gif
733 ms
brownCorners_topright.gif
782 ms
brownCorners_bottomleft.gif
780 ms
brownCorners_bottomright.gif
770 ms
cart.gif
709 ms
print.css
112 ms
roze.pl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
roze.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
roze.pl SEO score
PL
N/A
ISO-8859-2
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roze.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Roze.pl main page’s claimed encoding is iso-8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
roze.pl
Open Graph description is not detected on the main page of Roze. 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: