Tools & Wizards About Us
page.uplus.co.kr screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 0

    Best Practices

  • 82

    SEO

    Google-friendlier than
    44% of websites

page.uplus.co.kr

홈 | U+Page

Page Load Speed

6.9 sec in total

First Response

1.2 sec

Resources Loaded

5.5 sec

Page Rendered

262 ms

page.uplus.co.kr screenshot

About Website

Visit page.uplus.co.kr now to see the best up-to-date Page Uplus content for South Korea and also check out these interesting facts you probably never knew about page.uplus.co.kr

화제의 모바일 콘텐츠를 한 곳에서!

Visit page.uplus.co.kr

Key Findings

We analyzed Page.uplus.co.kr page load time and found that the first response time was 1.2 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

page.uplus.co.kr performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value19.5 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.522

15/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

page.uplus.co.kr

1160 ms

common.css

1351 ms

google.css

454 ms

pageanaly.js

515 ms

global.full.js

448 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 99% of them (70 requests) were addressed to the original Page.uplus.co.kr, 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Page.uplus.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.7 kB (77%)

Content Size

124.2 kB

After Optimization

28.5 kB

  • HTML
  • JavaScript

In fact, the total size of Page.uplus.co.kr main page is 124.2 kB. 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. HTML takes 71.3 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 63.7 kB

  • Original 71.3 kB
  • After minification 51.3 kB
  • After compression 7.6 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 20.0 kB, which is 28% 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 63.7 kB or 89% of the original size.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (14%)

Requests Now

70

After Optimization

60

  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Page Uplus. 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.

Network Requests Diagram

page.uplus.co.kr

page.uplus.co.kr

1160 ms

common.css

common.css

1351 ms

google.css

google.css

454 ms

pageanaly.js

pageanaly.js

515 ms

global.full.js

global.full.js

448 ms

index.js

index.js

462 ms

main.full.js

main.full.js

916 ms

analytics.js

analytics.js

46 ms

sprite_all.png

sprite_all.png

697 ms

img_logo.png

img_logo.png

515 ms

bullet_gnbmenu_home.png

bullet_gnbmenu_home.png

228 ms

bullet_gnbmenu_video.png

bullet_gnbmenu_video.png

227 ms

bullet_gnbmenu_gameapp.png

bullet_gnbmenu_gameapp.png

510 ms

bullet_gnbMenu_google.png

bullet_gnbMenu_google.png

230 ms

1pxDummy.png

1pxDummy.png

453 ms

mask_size02.png

mask_size02.png

453 ms

img_search_before1.gif

img_search_before1.gif

460 ms

img_search_before2.gif

img_search_before2.gif

677 ms

img_search_before3.gif

img_search_before3.gif

678 ms

btn_login.png

btn_login.png

688 ms

loding_01.gif

loding_01.gif

1020 ms

btn_certi.png

btn_certi.png

772 ms

banner_weatherDefault.png

banner_weatherDefault.png

901 ms

dummyImageBanner.png

dummyImageBanner.png

902 ms

1244x336.png

1244x336.png

916 ms

108x108.png

108x108.png

928 ms

img_gotop.png

img_gotop.png

1029 ms

close_layerpop.png

close_layerpop.png

1125 ms

btn_goto_google2.gif

btn_goto_google2.gif

1126 ms

btn_goto_googlep.gif

btn_goto_googlep.gif

1145 ms

btn_goto_img.gif

btn_goto_img.gif

1159 ms

btn_goto_news.gif

btn_goto_news.gif

1275 ms

btn_goto_gmap.gif

btn_goto_gmap.gif

1284 ms

btn_goto_youtube.gif

btn_goto_youtube.gif

1349 ms

btn_goto_gmail.gif

btn_goto_gmail.gif

1350 ms

btn_goto_drive.gif

btn_goto_drive.gif

1373 ms

btn_goto_gdate.gif

btn_goto_gdate.gif

1391 ms

btn_goto_translate.gif

btn_goto_translate.gif

1528 ms

btn_goto_blog.gif

btn_goto_blog.gif

1540 ms

btn_goto_pic.gif

btn_goto_pic.gif

1575 ms

btn_goto_video.gif

btn_goto_video.gif

1576 ms

btn_goto_groups.gif

btn_goto_groups.gif

1601 ms

btn_goto_shopping.gif

btn_goto_shopping.gif

1623 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

2022 ms

lgm.ns.min.js

lgm.ns.min.js

1834 ms

btn_goto_books.gif

btn_goto_books.gif

1577 ms

btn_googles_off.gif

btn_googles_off.gif

1576 ms

btn_goto_keep.gif

btn_goto_keep.gif

1382 ms

btn_goto_gmail2.gif

btn_goto_gmail2.gif

1404 ms

btn_goto_youtube2.gif

btn_goto_youtube2.gif

1571 ms

btn_goto_movie.gif

btn_goto_movie.gif

1521 ms

btn_goto_book.gif

btn_goto_book.gif

1555 ms

btn_goto_gdate2.gif

btn_goto_gdate2.gif

1415 ms

btn_goto_mapview.gif

btn_goto_mapview.gif

1577 ms

btn_goto_chrometophone.gif

btn_goto_chrometophone.gif

1568 ms

btn_goto_chrom.gif

btn_goto_chrom.gif

1604 ms

btn_goto_news2.gif

btn_goto_news2.gif

1545 ms

btn_goto_hangout.gif

btn_goto_hangout.gif

1389 ms

btn_goto_sheet.gif

btn_goto_sheet.gif

1421 ms

btn_goto_presentation.gif

btn_goto_presentation.gif

1563 ms

btn_goto_document.gif

btn_goto_document.gif

1551 ms

btn_goto_otp.gif

btn_goto_otp.gif

1502 ms

btn_goto_and_set.gif

btn_goto_and_set.gif

1526 ms

btn_goto_camera.gif

btn_goto_camera.gif

1446 ms

btn_goto_picasa.gif

btn_goto_picasa.gif

1429 ms

btn_goto_blogger.gif

btn_goto_blogger.gif

1559 ms

img_wiseSaying.png

img_wiseSaying.png

1546 ms

common.js

common.js

684 ms

globalForm.js

globalForm.js

742 ms

jquery.plugin-set.js

jquery.plugin-set.js

722 ms

lgm.m.min.js

lgm.m.min.js

1278 ms

Accessibility Review

page.uplus.co.kr accessibility score

50

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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.

SEO Factors

page.uplus.co.kr SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Page.uplus.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Page.uplus.co.kr 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

page.uplus.co.kr

Open Graph data is detected on the main page of Page Uplus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: