19.1 sec in total
260 ms
18.5 sec
349 ms
Click here to check amazing Oye content for Spain. Otherwise, check out these important facts you probably never knew about oye.fm
Wellcome to the brand new website of Itzurun Comunicaciones: ICC. ICC started up as a IT services company on 1994, at Zumaia, Spain, and got soon its main bussiness activity providing IT related servi...
Visit oye.fmWe analyzed Oye.fm page load time and found that the first response time was 260 ms and then it took 18.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
oye.fm performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.4 s
21/100
25%
Value12.2 s
3/100
10%
Value390 ms
69/100
30%
Value0.013
100/100
15%
Value7.7 s
45/100
10%
260 ms
1295 ms
171 ms
477 ms
366 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Oye.fm, 98% (81 requests) were made to Iccbroadcast.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.2 sec) relates to the external source Iccbroadcast.com.
Page size can be reduced by 1.0 MB (36%)
2.8 MB
1.8 MB
In fact, the total size of Oye.fm main page is 2.8 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 51.1 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 8.2 kB, which is 13% 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 51.1 kB or 82% of the original size.
Potential reduce by 191.0 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, Oye needs image optimization as it can save up to 191.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 420.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 420.2 kB or 74% of the original size.
Potential reduce by 348.0 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. Oye.fm needs all CSS files to be minified and compressed as it can save up to 348.0 kB or 85% of the original size.
Number of requests can be reduced by 46 (58%)
79
33
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oye. 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 25 to 1 for CSS and as a result speed up the page load time.
oye.fm
260 ms
1295 ms
wp-emoji-release.min.js
171 ms
477 ms
estilos.css
366 ms
styles.css
874 ms
settings.css
960 ms
style.css
878 ms
style.css
966 ms
style.css
635 ms
red.css
578 ms
font-awesome.css
672 ms
font-awesome-corp.css
747 ms
font-awesome-ext.css
1101 ms
font-awesome-social.css
927 ms
font-awesome-more-ie7.min.css
10188 ms
wpgmza_style.css
1623 ms
jquery.js
2667 ms
jquery-migrate.min.js
3028 ms
principal.js
2537 ms
jquery.themepunch.tools.min.js
1787 ms
jquery.themepunch.revolution.min.js
2685 ms
jquery.form.min.js
1960 ms
scripts.js
3747 ms
tinynav.js
2646 ms
hoverIntent.min.js
3021 ms
superfish.js
2723 ms
jquery.sticky.js
2803 ms
owl.carousel.js
4898 ms
jquery.fancybox.js
3770 ms
jquery.inview.js
3072 ms
nbw-parallax.js
3810 ms
pi.init.videoResize.min.js
3876 ms
wow.min.js
3838 ms
jquery.isotope.js
4239 ms
jquery.ui.totop.js
3898 ms
bootstrap.min.js
4792 ms
theme-options.js
3968 ms
main.js
3811 ms
bootstrap.min.css
5758 ms
bootstrap-theme.min.css
3777 ms
css
22 ms
jquery.fancybox.css
4566 ms
theme-options.css
4332 ms
animate.css
5108 ms
owl.carousel.css
4326 ms
owl.theme.css
5116 ms
owl.transitions.css
5072 ms
font-awesome.min.css
4996 ms
theme-responsive.css
5091 ms
us.png
293 ms
us.png
290 ms
logo_iccweb1.png
618 ms
consulting3.jpg
1267 ms
it-consulting5.jpg
1476 ms
mobile-apps-develop2.jpg
1396 ms
estaciontv.jpg
1982 ms
source-code2.jpg
2106 ms
video-on-demand2.jpg
1688 ms
233.png
2274 ms
205.png
2639 ms
87.png
2191 ms
486.png
3130 ms
484.png
4727 ms
spacial-audio-logo.png
2548 ms
apps4radio-logo1.png
2384 ms
ecohosting-logo2.png
3269 ms
fujitsu-logo1.png
3543 ms
streaming-pro-logo1.png
2738 ms
WinMedia-logo.png
2832 ms
partner-minicaster.png
3070 ms
partner-barix.png
3241 ms
partner-hardata.png
3305 ms
partner-audioscience.png
3604 ms
partner-mayah.png
3804 ms
partner-ovh.png
3532 ms
partner-axel.png
4639 ms
fontawesome-webfont.woff
6333 ms
fontawesome-webfont.woff
4993 ms
bullet.png
3553 ms
large_left.png
5017 ms
large_right.png
4346 ms
ui.totop.png
4667 ms
oye.fm accessibility score
oye.fm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
oye.fm 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oye.fm can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Oye.fm 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.
oye.fm
Open Graph data is detected on the main page of Oye. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: