6.3 sec in total
1.5 sec
4.6 sec
213 ms
Welcome to ottomedia.com homepage info - get ready to check Ottomedia best content right away, or after learning these important things about ottomedia.com
Visit ottomedia.comWe analyzed Ottomedia.com page load time and found that the first response time was 1.5 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ottomedia.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.9 s
14/100
25%
Value8.4 s
18/100
10%
Value1,600 ms
12/100
30%
Value0.152
75/100
15%
Value17.1 s
4/100
10%
1548 ms
1047 ms
47 ms
18 ms
27 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ottomedia.com, 38% (38 requests) were made to Cafeimgs.naver.net and 36% (36 requests) were made to Cafe.naver.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ottomedia.com.
Page size can be reduced by 722.3 kB (61%)
1.2 MB
465.4 kB
In fact, the total size of Ottomedia.com main page is 1.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. 60% of websites need less resources to load. Javascripts take 529.8 kB which makes up the majority of the site volume.
Potential reduce by 202 B
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 202 B or 38% of the original size.
Potential reduce by 26.6 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. Ottomedia images are well optimized though.
Potential reduce by 393.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 393.9 kB or 74% of the original size.
Potential reduce by 301.6 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. Ottomedia.com needs all CSS files to be minified and compressed as it can save up to 301.6 kB or 83% of the original size.
Number of requests can be reduced by 77 (77%)
100
23
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ottomedia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ottomedia.com
1548 ms
dreamalcy
1047 ms
mycafe-common-1456292137000-56089.css
47 ms
mycafe-layout-1456292137000-54983.css
18 ms
line_sticker-1456919627000-9159.css
27 ms
comment-1457060304000-16274.css
24 ms
mycafe-main-1457060569000-189828.css
28 ms
widget-1456292137000-14603.css
43 ms
moz_fix-1456292137000-1346.css
43 ms
cafe_map-1449046670000-14564.css
42 ms
JEagleEyeClient-1449046660000-16187.js
40 ms
jindo.all-1452761259000-122834.js
41 ms
cssquery-1449046660000-18676.js
53 ms
common_util-1449046657000-4535.js
52 ms
widget-1449046655000-2800.js
56 ms
cafe_common-1456292137000-24273.js
52 ms
cafe_eventutil-1449046664000-2096.js
53 ms
autosourcing-1449046657000-8747.js
53 ms
AjaxRequest-1449046661000-16024.js
55 ms
clickcr-1449046654000-6201.js
52 ms
lcslog-1449046656000-11106.js
58 ms
TabletHandler-1449046663000-2403.js
59 ms
skipNavigationWebkit-1449046668000-907.js
55 ms
KeywordHighlightOption-1449046661000-2154.js
54 ms
gnb_euckr.nhn
65 ms
URLEncodingMap_MS949-1449046656000-97750.js
54 ms
URLEncoder-1449046655000-2121.js
85 ms
favorite_cafe-1449046669000-1385.js
53 ms
Tablet-1449046657000-4233.js
83 ms
Menu-1449046663000-4245.js
53 ms
SocialAppUtil-1449046669000-1984.js
60 ms
ip_layer_2-1449046666000-2882.css
59 ms
OneToOneChatLauncher-1451282494000-1473.js
137 ms
cafe_ui-1449046657000-18304.js
138 ms
ico-blank.gif
248 ms
hidden.gif
487 ms
11200759_user_174536.jpg
695 ms
btn_close.gif
109 ms
btn-down-gnb.png
490 ms
ico-blank.gif
486 ms
ico_lock.gif
485 ms
ico-new.gif
487 ms
ico_layer.gif
488 ms
btn_clse_lay.gif
491 ms
btn_cfm_lay.gif
492 ms
btn_close_layer3.gif
492 ms
getLoginStatus.nhn
708 ms
promo_npay.png
88 ms
sepcial-menu-bg.gif
237 ms
sepcial-menu-line.gif
225 ms
layer_login.gif
474 ms
CafePopularityLogAjax.nhn
273 ms
adshow
1378 ms
btn_srch.gif
418 ms
tab_group_on.gif
419 ms
tab_group2.gif
425 ms
tab_group3.gif
426 ms
btn_bookmark_off.png
426 ms
bg_info_action.gif
420 ms
ico_manager.gif
422 ms
ico_sprite_ranktbl.gif
423 ms
ico_cnt_mem.gif
427 ms
btn_join.png
427 ms
menu-bg-t.gif
427 ms
menu-bg-m.gif
429 ms
ico-m-list.gif
427 ms
ico_cafe_kin.png
428 ms
menu-bg-tit.gif
429 ms
ico-m-link.gif
449 ms
btn-down-menu.gif
429 ms
ico-m-kin.gif
429 ms
menu-bg-b.gif
430 ms
0101_back.gif
430 ms
MyCafeIntro.nhn
458 ms
ico_cnt_bkmk.gif
167 ms
ico_cnt_bkmk2_20111028.gif
190 ms
ico_cnt_mbl.gif
167 ms
original_viewer-1456292137000-41869.js
5 ms
original_viewer.css
78 ms
lg_photoviewer.gif
80 ms
Carstera.gif
710 ms
list-tit-bg.gif
765 ms
btn-more.gif
72 ms
s_1114874.gif
705 ms
m
704 ms
s_8254.gif
635 ms
ico-list-notice.gif
10 ms
ico-img.gif
10 ms
ico-widget-tit.gif
12 ms
automall.jpg
655 ms
carup.jpg
655 ms
autooasis.jpg
645 ms
btn_left.gif
8 ms
btn_right.gif
10 ms
btn_original2.png
10 ms
btn_close.gif
10 ms
promo_npay_1603.png
4 ms
clickcrD.js
10 ms
btn-service-gnb.png
11 ms
sp_gnb_v10.png
7 ms
common.css
478 ms
ottomedia.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
[aria-*] attributes do not match their roles
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
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.
ottomedia.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ottomedia.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ottomedia.com 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ottomedia.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.
ottomedia.com
Open Graph description is not detected on the main page of Ottomedia. 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: