Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

iriver.com

IRIVER

Page Load Speed

10.4 sec in total

First Response

525 ms

Resources Loaded

9.7 sec

Page Rendered

138 ms

iriver.com screenshot

About Website

Visit iriver.com now to see the best up-to-date IRIVER content for Russia and also check out these interesting facts you probably never knew about iriver.com

아이리버는 사운드 제품 정체성을 유지하면서 생활 속 라이프 스타일 제품을 통해 고객의 라이프 스타일을 변화시킬 수 있는 가치를 만들고 있습니다.

Visit iriver.com

Key Findings

We analyzed Iriver.com page load time and found that the first response time was 525 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

iriver.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value40.3 s

0/100

25%

SI (Speed Index)

Value29.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.179

68/100

15%

TTI (Time to Interactive)

Value47.8 s

0/100

10%

Network Requests Diagram

iriver.com

525 ms

jquery-1.6.1.min.js

415 ms

common.js

399 ms

main.css

404 ms

common.css

207 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that all of those requests were addressed to Iriver.com and no external sources were called. The less responsive or slowest element that took the longest time to load (8.5 sec) belongs to the original domain Iriver.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (68%)

Content Size

2.0 MB

After Optimization

627.8 kB

In fact, the total size of Iriver.com main page is 2.0 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. 15% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.6 kB

  • Original 18.9 kB
  • After minification 16.0 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 2.9 kB, which is 15% 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 14.6 kB or 77% of the original size.

Image Optimization

-68%

Potential reduce by 1.2 MB

  • Original 1.8 MB
  • After minification 588.3 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, IRIVER needs image optimization as it can save up to 1.2 MB or 68% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 64.2 kB

  • Original 97.5 kB
  • After minification 96.6 kB
  • After compression 33.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 64.2 kB or 66% of the original size.

CSS Optimization

-72%

Potential reduce by 5.1 kB

  • Original 7.2 kB
  • After minification 6.3 kB
  • After compression 2.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. Iriver.com needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IRIVER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Review

iriver.com accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

iriver.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

iriver.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iriver.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed English language. Our system also found out that Iriver.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of IRIVER. 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: