9.5 sec in total
406 ms
8.7 sec
378 ms
Visit fomei.com now to see the best up-to-date FOMEI content for Czech Republic and also check out these interesting facts you probably never knew about fomei.com
V e-shopu najdete veškeré studiové vybavení, fotopapíry s podporou i dalekohledy a puškohledy.
Visit fomei.comWe analyzed Fomei.com page load time and found that the first response time was 406 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fomei.com performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value22.8 s
0/100
25%
Value13.3 s
2/100
10%
Value170 ms
93/100
30%
Value0.022
100/100
15%
Value21.2 s
1/100
10%
406 ms
1822 ms
27 ms
63 ms
314 ms
Our browser made a total of 174 requests to load all elements on the main page. We found that 75% of them (131 requests) were addressed to the original Fomei.com, 10% (18 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) relates to the external source Freegeoip.net.
Page size can be reduced by 1.1 MB (55%)
2.0 MB
910.0 kB
In fact, the total size of Fomei.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 935.4 kB which makes up the majority of the site volume.
Potential reduce by 60.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. This page needs HTML code to be minified as it can gain 18.6 kB, which is 25% 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 60.3 kB or 80% of the original size.
Potential reduce by 235.5 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, FOMEI needs image optimization as it can save up to 235.5 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 532.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 532.2 kB or 79% of the original size.
Potential reduce by 276.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. Fomei.com needs all CSS files to be minified and compressed as it can save up to 276.2 kB or 84% of the original size.
Number of requests can be reduced by 48 (32%)
150
102
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOMEI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
fomei.com
406 ms
www.fomei.com
1822 ms
css
27 ms
css
63 ms
62129f58-6367-4cef-89e1-7a4d197a7cb7-cs
314 ms
jquery.magnific-popup.css
253 ms
main.css
613 ms
shop.css
473 ms
shared.css
361 ms
jquery-ui.structure.min.css
321 ms
jquery-ui.theme.min.css
365 ms
jquery-ui.min.css
517 ms
jquery.tree.css
434 ms
widget_group_shared.js
801 ms
jquery.magnific-popup.min.js
579 ms
main.js
543 ms
modernizr.custom.16762.js
593 ms
html5shiv.js
625 ms
enquire.min.js
658 ms
jquery-ui.min.js
974 ms
jquery.tree.js
710 ms
WebResource.axd
727 ms
WebResource.axd
721 ms
shared.js
902 ms
generalList.js
883 ms
gjs.php
313 ms
widget.php
113 ms
analytics.js
47 ms
collect
3 ms
collect
55 ms
Pf_kZuIH5c5WKVkQUaeSWQ.ttf
51 ms
oM0rzUuPqVJpW-VEIpuW5w.ttf
52 ms
nLUBdz_lHHoVIPor05Byhw.ttf
29 ms
qa-Ci2pBwJdCxciE1ErifQ.ttf
51 ms
oVOtQy53isv97g4UhBUDqg.ttf
51 ms
YnSn3HsyvyI1feGSdRMYqA.ttf
51 ms
2DiK4XkdTckfTk6we73-bQ.ttf
52 ms
IVYl_7dJruOg8zKRpC8Hrw.ttf
53 ms
e8csG8Wnu87AF6uCndkFRQ.ttf
51 ms
print.css
115 ms
gtm.js
63 ms
icoCz.png
125 ms
icoSk.png
193 ms
icoEn.png
192 ms
icoPl.png
192 ms
image_of_object
195 ms
image_of_object
200 ms
image_of_object
261 ms
image_of_object
261 ms
image_of_object
259 ms
image_of_object
259 ms
image_of_object
310 ms
image_of_object
312 ms
image_of_object
364 ms
image_of_object
366 ms
image_of_object
367 ms
image_of_object
363 ms
image_of_object
423 ms
image_of_object
421 ms
image_of_object
456 ms
image_of_object
466 ms
image_of_object
469 ms
image_of_object
471 ms
image_of_object
529 ms
image_of_object
530 ms
image_of_object
560 ms
image_of_object
577 ms
image_of_object
579 ms
image_of_object
596 ms
image_of_object
637 ms
image_of_object
638 ms
image_of_object
664 ms
image_of_object
683 ms
image_of_object
687 ms
image_of_object
706 ms
image_of_object
745 ms
linkid.js
26 ms
ec.js
27 ms
conversion_async.js
30 ms
retargeting.js
365 ms
5527 ms
fbevents.js
20 ms
xxA5ZscX9sTU6U0lZJUlYA.ttf
20 ms
amzRVCB-gipwdihZZ2LtT_esZW2xOQ-xsNqO47m55DA.ttf
21 ms
iSy9VTeUTiqiurQg2ywtu_esZW2xOQ-xsNqO47m55DA.ttf
21 ms
DCrVxDVvS69n50O-5erZVvesZW2xOQ-xsNqO47m55DA.ttf
21 ms
LNYVgsJcaCxoKFHmd4AZcg.ttf
89 ms
Vmo58BiptGwfVFb0teU5gPesZW2xOQ-xsNqO47m55DA.ttf
92 ms
Sdo-zW-4_--pDkTg6bYrY_esZW2xOQ-xsNqO47m55DA.ttf
85 ms
p0TA6KeOz1o4rySEbvUxI_esZW2xOQ-xsNqO47m55DA.ttf
90 ms
KPhsGCoT2-7Uj6pMlRscH_esZW2xOQ-xsNqO47m55DA.ttf
89 ms
fontawesome-webfont.woff
871 ms
image_of_object
657 ms
collect
18 ms
collect
66 ms
79 ms
168 ms
image_of_object
615 ms
image_of_object
621 ms
image_of_object
637 ms
image_of_object
673 ms
image_of_object
679 ms
ga-audiences
110 ms
image_of_object
656 ms
image_of_object
662 ms
image_of_object
682 ms
image_of_object
727 ms
sdk.js
47 ms
image_of_object
694 ms
image_of_object
713 ms
20 ms
37 ms
image_of_object
668 ms
image_of_object
687 ms
image_of_object
721 ms
xd_arbiter.php
23 ms
xd_arbiter.php
32 ms
image_of_object
724 ms
image_of_object
676 ms
image_of_object
712 ms
image_of_object
686 ms
retargeting
110 ms
image_of_object
697 ms
image_of_object
728 ms
image_of_object
731 ms
image_of_object
681 ms
image_of_object
741 ms
image_of_object
712 ms
image_of_object
697 ms
image
725 ms
image
712 ms
image
673 ms
9d626845-86c4-4c9d-bc89-4a6353afa6cf-cs
848 ms
a93e8932-4236-4e0a-9fce-c8e8c0f0711b-cs
716 ms
0760f013-1a46-492d-b7d4-14b0a0cf10b6-cs
699 ms
9fe61206-d384-4ab2-bd10-2467806ff784-cs
724 ms
image_of_object
720 ms
image_of_object
668 ms
image_of_object
738 ms
image_of_object
710 ms
image
717 ms
image
696 ms
image
678 ms
image
719 ms
image
713 ms
image
705 ms
image
688 ms
image
650 ms
footerLogo.png
651 ms
hTNLi.png
706 ms
hTN0.png
710 ms
hTN1a.png
704 ms
hTN2a.png
678 ms
headerTel.png
654 ms
logo.png
667 ms
headerBasket.png
717 ms
menuA.png
698 ms
subNav.png
701 ms
sliderOdrazka.png
678 ms
4a07a4de-9582-4150-8182-418ccca90192
651 ms
2d2f93f1-260c-4e21-ad2c-f2774b1f1923
664 ms
39cdb14e-2d7e-4f77-97b1-41a2b21553aa
712 ms
d722e1cb-3e09-43df-9335-4eb175a16a4f
662 ms
image_of_object
787 ms
sliderTitle.png
675 ms
image_of_object
764 ms
image_of_object
771 ms
sliderNavLi.png
718 ms
newsBtn.png
655 ms
newsWrap.png
675 ms
fSaarchSpan.png
724 ms
footer.png
723 ms
hTN1.png
744 ms
hTN2.png
685 ms
fomei.com accessibility score
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fomei.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fomei.com SEO score
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
Document uses legible font sizes
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fomei.com can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Fomei.com 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.
fomei.com
Open Graph description is not detected on the main page of FOMEI. 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: