10.1 sec in total
1.4 sec
7.6 sec
1.1 sec
Visit designlog.org now to see the best up-to-date DESIGN LOG content for South Korea and also check out these interesting facts you probably never knew about designlog.org
디자인로그(DESIGN LOG), 디자인.디지털 컨버전스 웹진, All Things Design, 디자인 뉴스, 그래픽 강좌, IT 컬럼, 디지털 트렌드, SEO 정보 제공
Visit designlog.orgWe analyzed Designlog.org page load time and found that the first response time was 1.4 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
designlog.org performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value18.1 s
0/100
25%
Value22.0 s
0/100
10%
Value2,160 ms
6/100
30%
Value0.916
3/100
15%
Value36.4 s
0/100
10%
1385 ms
914 ms
70 ms
122 ms
981 ms
Our browser made a total of 170 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Designlog.org, 18% (30 requests) were made to Tistory1.daumcdn.net and 9% (15 requests) were made to Blog.kakaocdn.net. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Blog.kakaocdn.net.
Page size can be reduced by 1.9 MB (22%)
8.6 MB
6.7 MB
In fact, the total size of Designlog.org main page is 8.6 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. 80% 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. Images take 7.5 MB which makes up the majority of the site volume.
Potential reduce by 142.2 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 45.8 kB, which is 27% 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 142.2 kB or 84% of the original size.
Potential reduce by 1.6 MB
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, DESIGN LOG needs image optimization as it can save up to 1.6 MB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 119.7 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 119.7 kB or 13% of the original size.
Potential reduce by 7.2 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. Designlog.org needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 17% of the original size.
Number of requests can be reduced by 95 (61%)
155
60
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DESIGN LOG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
designlog.org
1385 ms
style.css
914 ms
js
70 ms
adsbygoogle.js
122 ms
style.css
981 ms
script.js
982 ms
jquery-3.5.1.min.js
90 ms
lightbox-v2.10.0.min.js
104 ms
tiara.min.js
106 ms
lightbox.min.css
117 ms
font.css
996 ms
content.css
996 ms
base.js
1379 ms
kakao.min.js
996 ms
js
59 ms
js
71 ms
webfonticon.css
1106 ms
slick.css
1141 ms
style.css
1144 ms
jquery.js
38 ms
slick.js
1352 ms
iscroll.js
1457 ms
front.js
1304 ms
common.js
1340 ms
revenue.css
1341 ms
dialog.css
1602 ms
font.css
102 ms
postBtn.css
1609 ms
comment.css
1609 ms
tistory.css
1609 ms
common.js
1609 ms
comment.js
2255 ms
wcslog.js
54 ms
search_dragselection.min.js
164 ms
default.min.css
14 ms
highlight.min.js
27 ms
delphi.min.js
27 ms
php.min.js
41 ms
python.min.js
26 ms
r.min.js
27 ms
ruby.min.js
28 ms
scala.min.js
41 ms
shell.min.js
40 ms
sql.min.js
39 ms
swift.min.js
39 ms
typescript.min.js
39 ms
vbnet.min.js
51 ms
roosevelt_dk_bt.js
898 ms
menubar.min.js
1964 ms
index.js
596 ms
polyfills-legacy.min.js
1034 ms
index-legacy.js
907 ms
oct.js
28 ms
show_ads_impl.js
224 ms
kakao.min.js
160 ms
analytics.js
18 ms
js
127 ms
js
127 ms
fbevents.js
127 ms
tracker.js
212 ms
SpoqaHanSans-kr.css
216 ms
sync
1625 ms
688767b269854d33b14c7408804e52e0
1447 ms
617 ms
img.jpg
2326 ms
img.jpg
2060 ms
img.png
3296 ms
img.png
2909 ms
img.jpg
2314 ms
img.jpg
2313 ms
img.png
2896 ms
img.png
2956 ms
img.png
3749 ms
img.jpg
2811 ms
img.jpg
3245 ms
img.jpg
3307 ms
img.jpg
3315 ms
img.jpg
3173 ms
img.jpg
4334 ms
1103 ms
1101 ms
1292 ms
1208 ms
1291 ms
1220 ms
1286 ms
1220 ms
1407 ms
1428 ms
1429 ms
1479 ms
ico_search.svg
517 ms
ico_menu.svg
513 ms
52811a78872748458e70296eec700415
515 ms
ico_facebook.svg
512 ms
ico_twitter.svg
1097 ms
ico_instagram.svg
1095 ms
ico_youtube.svg
1097 ms
ico_mail.svg
1094 ms
pv
157 ms
sdk.js
57 ms
bsa.js
328 ms
woopra.js
134 ms
js15.js
157 ms
SpoqaHanSansRegular.woff
141 ms
SpoqaHanSansLight.woff
272 ms
SpoqaHanSansThin.woff
405 ms
SpoqaHanSansBold.woff
407 ms
zrt_lookup.html
127 ms
ads
289 ms
ico_del.svg
853 ms
sdk.js
48 ms
200 ms
0.php
620 ms
ca-pub-2926960198422987
532 ms
img_common_tistory_190314.png
557 ms
api
1082 ms
Pretendard-Regular.woff
792 ms
prev.png
385 ms
next.png
331 ms
loading.gif
511 ms
close.png
612 ms
214 ms
adsct
179 ms
adsct
285 ms
ads
423 ms
ads
302 ms
ads
201 ms
ads
229 ms
ads
198 ms
ads
148 ms
ads
425 ms
ads
420 ms
219 ms
tag.min.js
21 ms
afwu.js
36 ms
423 ms
p
101 ms
v2
88 ms
tpid=51A01715927447E5753E24CEC75750B1
84 ms
nessie_icon_tiamat_white.png
109 ms
load_preloaded_resource.js
125 ms
abg_lite.js
364 ms
window_focus.js
364 ms
cookie_push_onload.html
49 ms
qs_click_protection.js
254 ms
ufs_web_display.js
98 ms
c653839755d9d9a3a773c62a0253f53f.js
91 ms
7167769925268475647
361 ms
icon.png
46 ms
dpixel
78 ms
sync
313 ms
405716.gif
398 ms
pixel
326 ms
pixel
210 ms
css
138 ms
i.match
276 ms
bounce
62 ms
3099908399795149086
56 ms
v2
32 ms
pixel
30 ms
activeview
138 ms
d4Vwwu8iHiCDxZ1xzxUGRbEaLZqCebWmAfX3l2eV90k.js
11 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff
136 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff
141 ms
generic
9 ms
pixel
14 ms
pixel
72 ms
sync
75 ms
pixel
15 ms
designlog.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
designlog.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
designlog.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
![]()
KO
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Designlog.org can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Designlog.org 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.
designlog.org
Open Graph data is detected on the main page of DESIGN LOG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: