2.2 sec in total
86 ms
846 ms
1.2 sec
Visit iloveklove.com now to see the best up-to-date Ilove KLOVE content and also check out these interesting facts you probably never knew about iloveklove.com
KLove 107.5 FM Los Angeles, CA - Aquí encontrarás la mejor música romántica POP del momento. | Univision
Visit iloveklove.comWe analyzed Iloveklove.com page load time and found that the first response time was 86 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
iloveklove.com performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value6.9 s
6/100
25%
Value3.5 s
87/100
10%
Value1,290 ms
18/100
30%
Value0.005
100/100
15%
Value14.9 s
8/100
10%
86 ms
60 ms
60 ms
75 ms
48 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iloveklove.com, 77% (55 requests) were made to Univision.com and 8% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (492 ms) relates to the external source Univision.com.
Page size can be reduced by 2.4 MB (46%)
5.2 MB
2.8 MB
In fact, the total size of Iloveklove.com main page is 5.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. Only a small number of websites need less resources to load. Javascripts take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 619.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 619.4 kB or 86% of the original size.
Potential reduce by 96.4 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. Ilove KLOVE images are well optimized though.
Potential reduce by 1.7 MB
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 1.7 MB or 50% of the original size.
Number of requests can be reduced by 51 (75%)
68
17
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ilove KLOVE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and as a result speed up the page load time.
iloveklove.com
86 ms
los-angeles-klve-fm
60 ms
gpp.stub.js
60 ms
otSDKStub.js
75 ms
polyfills-328d401eaa144085b1d8.js
48 ms
webpack-1a86042f2e0c8171c4b3.js
47 ms
framework.613d1112e6663248e48f.1715787128186.js
53 ms
a8dcba41424635229e6220dba528042d1ab0a2ce~a353122d.8d6f04bec2a86bf06afe.1715787128186.js
46 ms
main-0ef3833830070079ebf1.js
48 ms
9a867acda0013cdc3a484dab2cde4d35654b5b02~493df0b3.5c24dc316b73b552dd38.1715787128186.js
63 ms
9a867acda0013cdc3a484dab2cde4d35654b5b02~9722bd1d.fd3ee91b4fe1a52be172.1715787128186.js
68 ms
9a867acda0013cdc3a484dab2cde4d35654b5b02~c6ebb752.a95b831ee76777dad57e.1715787128186.js
222 ms
9a867acda0013cdc3a484dab2cde4d35654b5b02~f84fdedf.6a86dfddf114be51446a.1715787128186.js
218 ms
9a867acda0013cdc3a484dab2cde4d35654b5b02~7d46c53b.dbc8e65a665db51d9d88.1715787128186.js
220 ms
9a867acda0013cdc3a484dab2cde4d35654b5b02~a353122d.cd32dc415d4db60dc078.1715787128186.js
227 ms
_app-c6527fbe9725738078f0.js
243 ms
baedf866.a8cabaf9128678d395d7.1715787128186.js
226 ms
57b65b6ae930c93b3191e7b2fe43114379c032ed~4134d62c.6edb75e3f6edf2b77770.1715787128186.js
235 ms
591c38dc11a20461ca9907f84a04963b1647e2bc~493df0b3.f48017c40fe5f6c34939.1715787128186.js
236 ms
591c38dc11a20461ca9907f84a04963b1647e2bc~9722bd1d.a454e6f02b8201250b11.1715787128186.js
231 ms
591c38dc11a20461ca9907f84a04963b1647e2bc~ee80ce23.392dc77e210e9015dcf7.1715787128186.js
236 ms
591c38dc11a20461ca9907f84a04963b1647e2bc~f91a56ad.31fb76cd3303d8b8fbe2.1715787128186.js
234 ms
591c38dc11a20461ca9907f84a04963b1647e2bc~c8f34038.a53269c842169ae3be4c.1715787128186.js
362 ms
591c38dc11a20461ca9907f84a04963b1647e2bc~7d46c53b.09183fe5343ec5b73f09.1715787128186.js
237 ms
e52b03eb4097dd0ac992b091e09c6e0610ee9101~493df0b3.57efd9a0883e342064ff.1715787128186.js
238 ms
e52b03eb4097dd0ac992b091e09c6e0610ee9101~4134d62c.61970e9991ee0eed58fa.1715787128186.js
239 ms
2a4060d656ff4983a87deef05483fa99c79f64d5~4134d62c.6b360b6f664d85fe9d7d.1715787128186.js
238 ms
d9f9f87afc5bb6a87084fc773e6f38add4c199fb~493df0b3.355d200526ef02747423.1715787128186.js
250 ms
d9f9f87afc5bb6a87084fc773e6f38add4c199fb~9722bd1d.5eb6f91b9f2f1deb4bad.1715787128186.js
252 ms
d9f9f87afc5bb6a87084fc773e6f38add4c199fb~86e851a0.e86ab4955aff3ca875a1.1715787128186.js
251 ms
d9f9f87afc5bb6a87084fc773e6f38add4c199fb~801b6caf.7bb135ceff0623f4a2eb.1715787128186.js
367 ms
d9f9f87afc5bb6a87084fc773e6f38add4c199fb~a1dd2846.4d0aa5655a016f5b6f75.1715787128186.js
360 ms
b2d3b251f921e6eb9b25b10c6e4b8e54678d2b82~493df0b3.28f938da6c85795c1ee3.1715787128186.js
368 ms
b2d3b251f921e6eb9b25b10c6e4b8e54678d2b82~39e1814b.372ca02ff121f8899415.1715787128186.js
358 ms
afa7313a489315eb65becc461158e998d9608c8a~4134d62c.9ff367a271ee3f97e9ae.1715787128186.js
358 ms
afa7313a489315eb65becc461158e998d9608c8a~9722bd1d.51c0923d4116f97c2a6f.1715787128186.js
386 ms
afa7313a489315eb65becc461158e998d9608c8a~3ff9d9a6.14a7378136501fa07984.1715787128186.js
492 ms
afa7313a489315eb65becc461158e998d9608c8a~c8f34038.debb3531dc36c4efdf47.1715787128186.js
386 ms
afa7313a489315eb65becc461158e998d9608c8a~7d46c53b.0231445b49df08ba48d3.1715787128186.js
386 ms
gpt.js
232 ms
apstag.js
42 ms
13116.js
60 ms
jwplayer.js
46 ms
afa7313a489315eb65becc461158e998d9608c8a~13ca07a1.edc2799de20c8da6996a.1715787128186.js
371 ms
afa7313a489315eb65becc461158e998d9608c8a~3c3df127.fa66fd04437be30dcc0f.1715787128186.js
348 ms
afa7313a489315eb65becc461158e998d9608c8a~f71cff67.c750db9d9eb0164088f2.1715787128186.js
458 ms
univision-eaf3104cb058d2dbba74.js
441 ms
_buildManifest.js
464 ms
apstag.js
168 ms
_ssgManifest.js
456 ms
e7c2a27b-9c00-4eb3-adce-e9d5fa69f48f.json
160 ms
los-angeles107.5_white.svg
276 ms
logo-univision-color.49f6b4c4450cea582fa78cbc00dee7d8.1715787128354.svg
291 ms
radio-default-360.dcf11a68bc333d35a25ef923959df46f.1715787128354.jpg
290 ms
banner-desktop-1280-min.png
180 ms
striped-background.f987939b457a48df979571be9b1a8f2d.1715787128147.svg
290 ms
picture
336 ms
picture
399 ms
picture
329 ms
picture
327 ms
location
253 ms
picture
357 ms
striped-background.f987939b457a48df979571be9b1a8f2d.1715787128354.svg
277 ms
chevronUp.561ba0e1de362a1eebf2303f645c5bc2.1715787128354.svg
279 ms
default-content-image.71778a6d2a6b4d9051201b3a83177a50.1715787128354.png
298 ms
volumeHigh.fa5735d48d0298964077b0665dd4621e.1715787128354.svg
299 ms
close.d0f4dd4b1c11ed0fe676a8d88557ba40.1715787128354.svg
300 ms
pubads_impl.js
100 ms
otBannerSdk.js
46 ms
es.json
23 ms
otGPP.js
16 ms
iloveklove.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
[role]s are not contained by their required parent element
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.
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.
iloveklove.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
iloveklove.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iloveklove.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Iloveklove.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.
iloveklove.com
Open Graph data is detected on the main page of Ilove KLOVE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: