6.4 sec in total
1.8 sec
4.3 sec
303 ms
Click here to check amazing Neodigm content for South Korea. Otherwise, check out these important facts you probably never knew about neodigm.com
네오다임은 마케팅 기술을 기반으로 비즈니스 목표를 달성할 수 있는 온/오프라인 통합 마케팅 솔루션을 제공합니다.
Visit neodigm.comWe analyzed Neodigm.com page load time and found that the first response time was 1.8 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
neodigm.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value20.7 s
0/100
25%
Value17.7 s
0/100
10%
Value1,860 ms
9/100
30%
Value0.001
100/100
15%
Value30.8 s
0/100
10%
1810 ms
163 ms
84 ms
72 ms
82 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 28% of them (40 requests) were addressed to the original Neodigm.com, 49% (71 requests) were made to Vendor-cdn.imweb.me and 11% (16 requests) were made to Cdn.imweb.me. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Neodigm.com.
Page size can be reduced by 839.2 kB (53%)
1.6 MB
754.0 kB
In fact, the total size of Neodigm.com main page is 1.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. Only a small number of websites need less resources to load. HTML takes 758.0 kB which makes up the majority of the site volume.
Potential reduce by 671.9 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. 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 671.9 kB or 89% of the original size.
Potential reduce by 5.1 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, Neodigm needs image optimization as it can save up to 5.1 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 126.4 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 126.4 kB or 23% of the original size.
Potential reduce by 35.9 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. Neodigm.com needs all CSS files to be minified and compressed as it can save up to 35.9 kB or 14% of the original size.
Number of requests can be reduced by 104 (83%)
126
22
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neodigm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 84 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.neodigm.com
1810 ms
gtm.js
163 ms
vendor_blue_10.css
84 ms
vendor_red_10.css
72 ms
im_component.css
82 ms
alarm_menu.css
102 ms
function.css
103 ms
site.css
106 ms
site2.css
122 ms
iefix2.css
105 ms
animate.css
140 ms
chosen.css
142 ms
chosenImage.css
143 ms
style.css
144 ms
ii.css
142 ms
pretendardvariable.css
149 ms
pretendard.css
149 ms
style.css
144 ms
custom.cm
291 ms
tailwind.css
143 ms
emoji.css
149 ms
font-awesome5.min.css
153 ms
notosanskr-hestia.css
6 ms
nanumgothic.css
30 ms
jquery.js
20 ms
jquery-ui.design.js
31 ms
lodash.min.js
30 ms
vue.global.prod.js
99 ms
axios.min.js
28 ms
loader.js
116 ms
widgets.js
138 ms
postcode.v2.js
169 ms
player.js
139 ms
bootstrap.min.js
60 ms
jquery.fileupload.js
59 ms
jquery.lazyload.min.js
60 ms
KR_KRW_currency.js
529 ms
common.js
58 ms
im_component.js
58 ms
site_common.js
61 ms
imagesloaded.pkgd.min.js
67 ms
jquery.smooth-scroll.min.js
67 ms
gambit-smoothscroll-min.js
67 ms
ThreeCanvas.js
67 ms
snow.js
66 ms
masonry.pkgd.min.js
77 ms
lightgallery-all.min.js
77 ms
bootstrap.slide-menu.js
77 ms
bootstrap.slide-menu-alarm.js
78 ms
bootstrap-hover-dropdown.min.js
77 ms
jquery-scrolltofixed.js
76 ms
jquery.trackpad-scroll-emulator.js
78 ms
modernizr.custom.js
80 ms
classie.js
80 ms
jquery.exif.js
78 ms
jquery.canvasResize.js
80 ms
autosize.js
79 ms
owl.carousel2.js
83 ms
slick.min.js
80 ms
preview_mode.js
470 ms
site.js
328 ms
site_member.js
328 ms
mobile_menu.js
468 ms
sns_share.js
469 ms
android_image_upload.js
517 ms
alarm_menu.js
677 ms
alarm_badge.js
767 ms
one_page.js
763 ms
site_coupon.js
768 ms
secret_article.js
849 ms
article_reaction.js
870 ms
site_shop.js
1202 ms
board_common.js
940 ms
site_shop_mypage.js
1294 ms
site_search.js
1118 ms
zipcode_daum.js
1027 ms
site_booking.js
1219 ms
site_section.js
1114 ms
jquery.number.min.js
78 ms
nprogress.js
76 ms
tinycolor-min.js
75 ms
app.js
1203 ms
header_fixed_menu.js
1288 ms
header_more_menu.js
1301 ms
header_center_colgroup.js
1592 ms
mobile_carousel_menu.js
1379 ms
header_mega_dropdown.js
1395 ms
header_overlay.js
1696 ms
site_log.js
1646 ms
advanced_trace.js
1472 ms
site_animation.js
1726 ms
site_event_check.js
1570 ms
site_widget.js
1871 ms
moment.min.js
75 ms
moment-with-locales.js
76 ms
bootstrap-datepicker.js
76 ms
jquery.timepicker.min.js
76 ms
channel_plugin.js
1917 ms
device_uuid.js
1768 ms
wcslog.js
99 ms
newest_post.js
1822 ms
ie-checker-min.js
64 ms
jquery.chosen.js
63 ms
vue.global.prod.js
28 ms
munchkin.js
196 ms
9b68e812a5f7a.jpg
177 ms
default_profile.png
1702 ms
9f53979328b32.jpg
156 ms
1c1312ddd44f0.jpg
156 ms
65de548fa36a1.png
213 ms
e5e97f6cb86e3.png
212 ms
e9f85379c2ce0.jpg
213 ms
bcac3aca95ca3.jpg
867 ms
47987e18f1ac9.jpg
269 ms
8641e5bd7aac8.jpg
870 ms
355c053ae0960.jpg
270 ms
967656d4c1820.jpg
880 ms
cf3e2651ae096.jpg
271 ms
56edeeae0fed4.jpeg
941 ms
0fd338e9e438c.png
925 ms
5c9b1e9f091bc.png
272 ms
5c8a52202c4e8.png
272 ms
NotoSansKR-Regular-Hestia.woff
33 ms
NotoSansKR-Medium-Hestia.woff
33 ms
NotoSansKR-Light-Hestia.woff
89 ms
NotoSansKR-Thin-Hestia.woff
90 ms
NotoSansKR-Bold-Hestia.woff
89 ms
NotoSansKR-Black-Hestia.woff
32 ms
PN_3Rfi-oW3hYwmKDpxS7F_D-djY5Hkr3w.woff
151 ms
PN_oRfi-oW3hYwmKDpxS7F_LQv3LyVsg9YUUUA.woff
152 ms
PN_oRfi-oW3hYwmKDpxS7F_LXv7LyVsg9YUUUA.woff
152 ms
Simple-Line-Icons.ttf
145 ms
BlackTie-Medium-webfont.woff
146 ms
BlackTie-Light-webfont.woff
146 ms
BlackTie-Bold-webfont.woff
145 ms
BlackTie-Solid-webfont.woff
144 ms
Plipop-Social-Icons.ttf
146 ms
Plipop-Social-Icons.ttf
147 ms
munchkin.js
144 ms
flag_kr_circle.png
1578 ms
flag_kr_square.png
1636 ms
visitWebPage
74 ms
iframe_api
38 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
61 ms
www-widgetapi.js
4 ms
neodigm.com 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
Links do not have a discernible name
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.
neodigm.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
neodigm.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
KO
![]()
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neodigm.com 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 Neodigm.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.
neodigm.com
Open Graph data is detected on the main page of Neodigm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: