8.8 sec in total
401 ms
8.1 sec
262 ms
Visit apex-arch.cz now to see the best up-to-date APEX Arch content and also check out these interesting facts you probably never knew about apex-arch.cz
Projekty rodinných domů, online katalog rodinných domů, architektura na míru.
Visit apex-arch.czWe analyzed Apex-arch.cz page load time and found that the first response time was 401 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
apex-arch.cz performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value10.3 s
0/100
25%
Value14.6 s
1/100
10%
Value8,950 ms
0/100
30%
Value0.067
97/100
15%
Value20.6 s
2/100
10%
401 ms
149 ms
260 ms
264 ms
238 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 90% of them (70 requests) were addressed to the original Apex-arch.cz, 5% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to C.imedia.cz. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Apex-arch.cz.
Page size can be reduced by 735.1 kB (16%)
4.5 MB
3.8 MB
In fact, the total size of Apex-arch.cz main page is 4.5 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. 55% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 92.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 92.3 kB or 88% of the original size.
Potential reduce by 150.8 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. APEX Arch images are well optimized though.
Potential reduce by 358.4 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 358.4 kB or 71% of the original size.
Potential reduce by 133.6 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. Apex-arch.cz needs all CSS files to be minified and compressed as it can save up to 133.6 kB or 87% of the original size.
Number of requests can be reduced by 43 (57%)
76
33
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of APEX Arch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.apex-arch.cz
401 ms
wp-emoji-release.min.js
149 ms
styles.css
260 ms
page-list.css
264 ms
jquery.fancybox-1.3.4.css
238 ms
screen.css
248 ms
style.basic.css
268 ms
style-simple-red.css
275 ms
asljquery.js
464 ms
jquery.gestures.js
371 ms
jquery.easing.js
364 ms
jquery.mousewheel.js
374 ms
jquery.mCustomScrollbar.js
487 ms
jquery.ajaxsearchlite.js
489 ms
jquery.js
580 ms
jquery-migrate.min.js
510 ms
jquery.fancybox-1.3.4.pack.js
529 ms
jquery.bgPos.js
624 ms
jquery.color.js
637 ms
rotate.js
642 ms
ahover.js
660 ms
main.js
656 ms
run_ahover.js
721 ms
index.js
763 ms
coopToNew.js
803 ms
thumbs.js
800 ms
customInput.js
795 ms
style.css
777 ms
retargeting.js
352 ms
css
58 ms
analytics.js
128 ms
n%C3%A1vrhy-interi%C3%A9ru.jpg
518 ms
body.bg.gif
265 ms
main.bg.gif
256 ms
hdline.gif
188 ms
logo-apex.gif
188 ms
double_dotted_x.gif
153 ms
menubg2.png
260 ms
menubg.png
304 ms
dotted_y.gif
297 ms
search.gif
395 ms
nav.png
389 ms
fr0bg1.png
401 ms
fr0bg2.png
446 ms
detsky-sen-P1.jpg
967 ms
detsky-sen-P2.jpg
954 ms
aura-P1.jpg
1107 ms
aura-P2.jpg
1052 ms
vizia-P1.jpg
964 ms
vizia-P2.jpg
1149 ms
%C5%BEivi%C3%B31.jpg
1294 ms
%C5%BEivi%C3%B32.jpg
1356 ms
SKORPionik-P1.jpg
1285 ms
SKORPionik-P2.jpg
1599 ms
we-feel-good-P1.jpg
1468 ms
we-feel-good-P2.jpg
1646 ms
Panorama-P2.jpg
1675 ms
Panorama-P1.jpg
1635 ms
METROPOLITAN-2015-P1.jpg
1703 ms
METROPOLITAN-2015-P2.jpg
1770 ms
wh_bg.png
1992 ms
dotted_x_white.gif
1753 ms
novenavrhydomov2015.jpg
1841 ms
titulka_APEX2016.jpg
1964 ms
lfr_lnk_bg.png
1880 ms
lfr_lnk_bg2.png
1889 ms
analytics.js
63 ms
wahl_B.jpg
1960 ms
retargeting
129 ms
collect
12 ms
collect
7 ms
redbg.jpg
1836 ms
meszaros-P2_4NEW.jpg
1978 ms
front.dom.jpg
1846 ms
ftline.gif
1835 ms
dt_bg.gif
1849 ms
dt_bg2.gif
1891 ms
www.apex-arch.cz
1626 ms
apex-arch.cz accessibility score
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
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.
apex-arch.cz 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
apex-arch.cz 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
SK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apex-arch.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it does not match the claimed Slovak language. Our system also found out that Apex-arch.cz 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.
apex-arch.cz
Open Graph data is detected on the main page of APEX Arch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: