8.5 sec in total
1.5 sec
6.1 sec
924 ms
Welcome to ico.eu homepage info - get ready to check ICO best content right away, or after learning these important things about ico.eu
Visit ico.euWe analyzed Ico.eu page load time and found that the first response time was 1.5 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ico.eu performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value17.0 s
0/100
25%
Value24.8 s
0/100
10%
Value15,960 ms
0/100
30%
Value0.395
26/100
15%
Value32.5 s
0/100
10%
1514 ms
216 ms
247 ms
243 ms
388 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 68% of them (40 requests) were addressed to the original Ico.eu, 12% (7 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ico.eu.
Page size can be reduced by 2.3 MB (73%)
3.2 MB
870.6 kB
In fact, the total size of Ico.eu main page is 3.2 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. CSS take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 93.4 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 93.4 kB or 84% of the original size.
Potential reduce by 10.1 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. ICO images are well optimized though.
Potential reduce by 735.3 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 735.3 kB or 67% of the original size.
Potential reduce by 1.5 MB
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. Ico.eu needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 89% of the original size.
Number of requests can be reduced by 29 (59%)
49
20
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ICO. 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 10 to 1 for CSS and as a result speed up the page load time.
www.ico.eu
1514 ms
wp-emoji-release.min.js
216 ms
settings.css
247 ms
main.min.css
243 ms
theme-styles.min.css
388 ms
theme-icons.min.css
365 ms
css
29 ms
style.css
241 ms
custom.css
332 ms
js_composer.css
647 ms
jquery.js
477 ms
jquery-migrate.min.js
361 ms
jquery.themepunch.tools.min.js
565 ms
jquery.themepunch.revolution.min.js
472 ms
head-scripts.js
471 ms
core.min.js
413 ms
widget.min.js
538 ms
tabs.min.js
536 ms
comment-reply.min.js
535 ms
scripts-vendors-ck.js
915 ms
smoothscroll.js
639 ms
jquerytransit.js
654 ms
js_composer_front.js
656 ms
player_api
23 ms
theme-styles.min-blessed1.css
619 ms
icologotrim-83.png
228 ms
logored.png
250 ms
Rd4B54aMOVo
223 ms
icologo-white.png
166 ms
paperworld-logo.png
170 ms
shadow-divider.png
168 ms
markerek.jpg
174 ms
iroszerek.jpg
584 ms
promotional-p-v2.jpg
583 ms
video-mask.png
582 ms
boxer2.jpg
582 ms
school-products.jpg
582 ms
fuzojukaszto.jpg
576 ms
antibacterial-v2.jpg
858 ms
accesories-v2.jpg
937 ms
hobby-prod.jpg
937 ms
europeanmanufacturer.png
935 ms
www-embed-player-vflfNyN_r.css
410 ms
www-embed-player.js
435 ms
base.js
502 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
409 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
412 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
413 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
414 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
413 ms
Pe-icon-line.woff
768 ms
ga.js
402 ms
www-widgetapi.js
211 ms
fontawesome-webfont.woff
488 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
292 ms
ad_status.js
188 ms
__utm.gif
239 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
106 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
106 ms
ico.eu 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.
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.
ico.eu 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
ico.eu 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
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
HU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ico.eu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Hungarian language. Our system also found out that Ico.eu 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.
ico.eu
Open Graph description is not detected on the main page of ICO. 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: