4.6 sec in total
1 sec
3.2 sec
373 ms
Click here to check amazing Edb content. Otherwise, check out these important facts you probably never knew about edb.net
European databank. Inquiry service. The most frequently used searchable on-line database of the Czech firms. Detailed maintained information on companies, their products and services from The Czech Re...
Visit edb.netWe analyzed Edb.net page load time and found that the first response time was 1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
edb.net performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.8 s
15/100
25%
Value4.6 s
71/100
10%
Value320 ms
76/100
30%
Value0.055
98/100
15%
Value6.6 s
57/100
10%
1037 ms
322 ms
439 ms
227 ms
232 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Edb.net, 28% (18 requests) were made to Edb.cz and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Edb.eu.
Page size can be reduced by 545.0 kB (52%)
1.1 MB
508.7 kB
In fact, the total size of Edb.net main page is 1.1 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. 40% of websites need less resources to load. Images take 476.6 kB which makes up the majority of the site volume.
Potential reduce by 65.2 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 65.2 kB or 76% of the original size.
Potential reduce by 122.9 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, Edb needs image optimization as it can save up to 122.9 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 309.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 309.1 kB or 71% of the original size.
Potential reduce by 47.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. Edb.net needs all CSS files to be minified and compressed as it can save up to 47.8 kB or 83% of the original size.
Number of requests can be reduced by 21 (33%)
63
42
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
czech-companies
1037 ms
Homepage.css
322 ms
jquery-1.11.3.min.js
439 ms
toggle_search_params.class.js
227 ms
app.js
232 ms
responsive.js
240 ms
WebResource.axd
332 ms
WebResource.axd
232 ms
ScriptResource.axd
242 ms
ScriptResource.axd
491 ms
ScriptResource.axd
319 ms
default.aspx
372 ms
WebResource.axd
373 ms
analytics.js
30 ms
count.asp
238 ms
t37483x1.png
417 ms
t55425x1.png
440 ms
t6319x1.png
460 ms
t55183x1.png
458 ms
t6308x1.png
472 ms
t54457x1.png
467 ms
t49335x1.png
515 ms
t6286x1.png
553 ms
t20160x1.png
574 ms
t54373x1.png
686 ms
t54281x1.png
586 ms
t38140x1.png
707 ms
t41530x1.png
620 ms
t6273x1.png
665 ms
t54075x1.png
689 ms
t54063x1.png
703 ms
t54060x1.png
725 ms
Image.aspx
115 ms
lang_cz.png
117 ms
lang_ge.png
109 ms
lang_sk.png
120 ms
lang_pl.png
115 ms
lang_it.png
232 ms
lang_es.png
316 ms
home.gif
317 ms
collect
11 ms
collect
71 ms
collect
27 ms
collect
78 ms
dot.asp
233 ms
vstup.htm
593 ms
bg.jpg
113 ms
top_yellow_box.png
111 ms
filter_vertical_line.jpg
110 ms
filters_arrows.png
132 ms
col_shadow.jpg
118 ms
dot.png
115 ms
pr_clanky_header_new.jpg
215 ms
shd.jpg
219 ms
arrow_bottom_brown.jpg
220 ms
plus.jpg
229 ms
contact-us_button.jpg
349 ms
header-en.png
253 ms
dot.png
320 ms
fb.png
331 ms
youtube.png
332 ms
g.png
336 ms
footer.jpg
371 ms
dot.asp
212 ms
edb.net 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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
edb.net 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
edb.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edb.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Edb.net main page’s claimed encoding is windows-1252. 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.
edb.net
Open Graph description is not detected on the main page of Edb. 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: