Tools & Wizards About Us
veckon.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

veckon.com

Veckon - Design your onff line life. - Veckon.com

Page Load Speed

2.2 sec in total

First Response

401 ms

Resources Loaded

1.7 sec

Page Rendered

114 ms

veckon.com screenshot

About Website

Welcome to veckon.com homepage info - get ready to check Veckon best content right away, or after learning these important things about veckon.com

Veckon is the real-time video communication service by WebRTC. Veckon.com will design your OnFF line life. 베컨.

Visit veckon.com

Key Findings

We analyzed Veckon.com page load time and found that the first response time was 401 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

veckon.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

www.veckon.com

401 ms

nanumgothic.css

38 ms

css

56 ms

css

61 ms

jsapi

25 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 38% of them (23 requests) were addressed to the original Veckon.com, 13% (8 requests) were made to Apis.google.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (514 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.3 kB (26%)

Content Size

673.7 kB

After Optimization

498.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Veckon.com main page is 673.7 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. 75% 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. Javascripts take 386.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 23.3 kB

  • Original 29.6 kB
  • After minification 20.7 kB
  • After compression 6.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 8.9 kB, which is 30% 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 23.3 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 49.5 kB

  • Original 231.2 kB
  • After minification 181.7 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, Veckon needs image optimization as it can save up to 49.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 96.9 kB

  • Original 386.9 kB
  • After minification 386.8 kB
  • After compression 290.0 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 96.9 kB or 25% of the original size.

CSS Optimization

-22%

Potential reduce by 5.7 kB

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 20.4 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. Veckon.com needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (49%)

Requests Now

51

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Veckon. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.veckon.com

www.veckon.com

401 ms

nanumgothic.css

nanumgothic.css

38 ms

css

css

56 ms

css

css

61 ms

jsapi

jsapi

25 ms

veckon.min.css

veckon.min.css

164 ms

js

js

78 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

138 ms

bootstrap.3.min.js

bootstrap.3.min.js

111 ms

html5shiv.ext.html5.js

html5shiv.ext.html5.js

136 ms

ajax.chromeframe.CFInstall.min.js

ajax.chromeframe.CFInstall.min.js

110 ms

veckon.index.min.js

veckon.index.min.js

110 ms

veckon.login.min.js

veckon.login.min.js

151 ms

loader.js

loader.js

22 ms

js

js

115 ms

analytics.js

analytics.js

138 ms

like.php

like.php

302 ms

widgets.js

widgets.js

411 ms

veckon_ci_100.png

veckon_ci_100.png

305 ms

f_logo.png

f_logo.png

133 ms

twitter_logo.png

twitter_logo.png

183 ms

veckon_bg_gray.png

veckon_bg_gray.png

410 ms

veckon_title_main_w.png

veckon_title_main_w.png

133 ms

veckon_triple.png

veckon_triple.png

126 ms

icon_freedom.png

icon_freedom.png

304 ms

icon_whenever.png

icon_whenever.png

305 ms

icon_easy.png

icon_easy.png

305 ms

joyComm.png

joyComm.png

307 ms

icon_realtime.png

icon_realtime.png

407 ms

webrtc.png

webrtc.png

404 ms

icon_userguide.png

icon_userguide.png

408 ms

icon_veckon.png

icon_veckon.png

407 ms

PN_3Rfi-oW3hYwmKDpxS7F_D-djb.ttf

PN_3Rfi-oW3hYwmKDpxS7F_D-djb.ttf

131 ms

PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsj.ttf

PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsj.ttf

173 ms

PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsj.ttf

PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsj.ttf

185 ms

plusone.js

plusone.js

104 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

146 ms

NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf

NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf

145 ms

client:plusone.js

client:plusone.js

133 ms

veckon_triple_cundefined.png

veckon_triple_cundefined.png

387 ms

js

js

85 ms

collect

collect

51 ms

collect

collect

171 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

137 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

135 ms

fastbutton

fastbutton

135 ms

js

js

128 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

93 ms

lbpnszsgnY_.js

lbpnszsgnY_.js

128 ms

FEppCFCt76d.png

FEppCFCt76d.png

126 ms

postmessageRelay

postmessageRelay

123 ms

developers.google.com

developers.google.com

514 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

151 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

22 ms

rpc:shindig_random.js

rpc:shindig_random.js

13 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

settings

settings

78 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

70 ms

embeds

embeds

21 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

78 ms

Accessibility Review

veckon.com accessibility score

73

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

veckon.com best practices score

50

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

veckon.com SEO score

77

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

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Veckon.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Veckon.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

veckon.com

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