22.8 sec in total
244 ms
22 sec
525 ms
Click here to check amazing I Word content for South Korea. Otherwise, check out these important facts you probably never knew about i.word.com
Find definitions for over 300,000 words from the most authoritative English dictionary. Continuously updated with new words and meanings.
Visit i.word.comWe analyzed I.word.com page load time and found that the first response time was 244 ms and then it took 22.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
i.word.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value5.0 s
26/100
25%
Value12.7 s
3/100
10%
Value5,660 ms
0/100
30%
Value0.01
100/100
15%
Value28.9 s
0/100
10%
244 ms
187 ms
27 ms
55 ms
147 ms
Our browser made a total of 295 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original I.word.com, 8% (24 requests) were made to Assets2.merriam-webster.com and 8% (23 requests) were made to Us-u.openx.net. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Acxiom.com.
Page size can be reduced by 1.8 MB (58%)
3.0 MB
1.3 MB
In fact, the total size of I.word.com main page is 3.0 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 136.7 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 136.7 kB or 75% of the original size.
Potential reduce by 22.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. I Word images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 63% of the original size.
Potential reduce by 591.7 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. I.word.com needs all CSS files to be minified and compressed as it can save up to 591.7 kB or 87% of the original size.
Number of requests can be reduced by 178 (69%)
257
79
The browser has sent 257 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Word. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
i.word.com
244 ms
www.merriam-webster.com
187 ms
www.merriam-webster.com
27 ms
style.min.css
55 ms
main.min.js
147 ms
art19-web-player-full.min-9afc6f69b5f8fbb15461abd9e2b41969.js
135 ms
heap-537798487.js
307 ms
MW_logo.png
302 ms
image1067229137-4171-31026b94dc04ce5cb688e6697560e4e2@1x.jpg
216 ms
alt-59ae0bb8ed5df-4180-d017ccc5442f97cfa3567dea7cf7bdff@1x.jpg
246 ms
trend-watch-quiz-eclipse-edition-4155-36d805d54700e9d5d03300889afce437@1x.jpg
250 ms
time-traveler-promo-cat-wow-4092-cca1a3cc344213b65eb74249e99a1f3f@1x.jpg
273 ms
video-title-words-of-the-year-1066-3955-139e53e2b370c61ee41c7039c282846b@1x.jpg
294 ms
header-social-sprite@2x.png
271 ms
quiz-carat.png
272 ms
subscribe-caret.png
269 ms
btn.menu.close@2x.png
271 ms
icon_header_mobile_FB_default@2x.png
271 ms
icon_header_mobile_twitter_default@2x.png
306 ms
icon_header_mobile_youtube_default@2x.png
305 ms
icon_header_mobile_ig_default@2x.png
306 ms
slider-ad-bg.png
306 ms
261x174@1x.jpg
306 ms
icon.pron@2x.png
306 ms
word-of-the-day-bottom.png
417 ms
video-play-button.png
321 ms
video-play-button-small.png
320 ms
MWLogo-BW.png
336 ms
fb-footer-icon.png
320 ms
tw-footer-icon.png
320 ms
gplay-footer-icon.png
448 ms
ig-footer-icon.png
448 ms
css
415 ms
font-awesome.min.css
330 ms
e835a9c9-df56-4625-82be-ecde75b5b708
424 ms
art19-logo-dark-bd0c7b70b5236d01e33c5094b6c21dae.png
117 ms
aquant.js
297 ms
jstag
292 ms
htw-merriam-webster.js
293 ms
analytics.js
162 ms
related-content-icon-sprite-semitransparent.png
237 ms
jwplayer.js
229 ms
h
222 ms
art19.min.css
23 ms
collect
36 ms
fontello-684dd82b3e711ad9838fe2776c6cb149.woff
35 ms
collect
118 ms
polyfills.promise.js
29 ms
polyfills.intersection-observer.js
49 ms
publishertag.js
122 ms
gpt.js
108 ms
rules-p-2a93ALTZSnZrY.js
158 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
114 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
156 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
258 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
259 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
277 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
277 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
277 ms
UC3ZEjagJi85gF9qFaBgIETamuWRjOQSPxoOXgdYd7c.ttf
277 ms
2NBgzUtEeyB-Xtpr9bm1Cczai8e7xzqnKiVb1EwOy0E.ttf
277 ms
video-title-words-of-the-year-1066-3955-6b32fb498e5dee26db5562a98bf49468@1x.jpg
10 ms
payday-2492-a86556aedfd5e5861c6c00388c92d4b5@1x.jpg
20 ms
decimate-video-1759-907dcfa3a9605515e8d99d34ce307f7d@1x.jpg
21 ms
serial-comma-3441@1x.jpg
20 ms
googima.js
92 ms
jwpsrv.js
107 ms
related.js
147 ms
jwplayer.controls.js
145 ms
pubads_impl_147.js
171 ms
beacon
141 ms
pixel;r=1477554127;a=p-2a93ALTZSnZrY;rf=0;uh=65ce955d6ae6;fpan=1;fpa=P0-578740937-1504686248083;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504686248083;tzo=-180;ref=;url=https%3A%2F%2Fwww.merriam-webster.com%2F;ogl=title.Dictionary%20by%20Merriam-Webster%3A%20America's%20most-trusted%20online%20dictionary%2Cimage.https%3A%2F%2Fassets2%252Emerriam-webster%252Ecom%2Fmw%2Fstatic%2Fsocial-media-share%2Fmw-logo-245x245%2Curl.https%3A%2F%2Fwww%252Emerriam-webster%252Ecom%2F%2Cdescription.The%20dictionary%20by%20Merriam-Webster%20is%20America's%20most%20trusted%20online%20dictionary%20fo%2Ctype.article
173 ms
user_sync.html
257 ms
0608867b
238 ms
bid
294 ms
cygnus
299 ms
bid
237 ms
cygnus
298 ms
bid
303 ms
cygnus
290 ms
container.html
186 ms
jpt
197 ms
jpt
195 ms
jpt
195 ms
jpt
195 ms
jpt
205 ms
jpt
202 ms
arj
451 ms
merge
97 ms
generic
95 ms
showad.js
38 ms
arj
438 ms
merge
73 ms
blank.gif
37 ms
js
55 ms
PugMaster
75 ms
acj
45 ms
acj
218 ms
acj
31 ms
arj
319 ms
merge
47 ms
merge
33 ms
0608867b
13 ms
img
13 ms
merge
7 ms
merge
7 ms
p-P7x87XHnVfbWr.gif
63 ms
generic
22 ms
merge
19 ms
Pug
94 ms
Pug
72 ms
Pug
71 ms
iframe
29 ms
Pug
39 ms
Pug
48 ms
Pug
42 ms
img
21 ms
img
29 ms
generic
11 ms
receive
20 ms
Pug
18 ms
bo
7 ms
merge
3 ms
pd
23 ms
3fc47beb-e127-a7c5-43a3-112321477654
145 ms
pixelssl.htm
193 ms
openx
5 ms
pixel
37 ms
sd
33 ms
sd
45 ms
sd
24 ms
sd
26 ms
acxiom.com
20032 ms
pd
19 ms
p2
32 ms
OpenX.ashx
238 ms
ox_match
99 ms
sd
44 ms
headerstats
36 ms
ads
217 ms
headerstats
33 ms
pd
31 ms
ads
397 ms
sd
20 ms
sd
20 ms
headerstats
18 ms
ads
581 ms
sd
14 ms
openx
76 ms
cksync.php
100 ms
1
91 ms
eox
79 ms
sd
29 ms
sd
52 ms
cfcm.ashx
52 ms
dds
40 ms
sd
36 ms
sd
26 ms
sd
26 ms
sd
5 ms
sd
7 ms
ecc
26 ms
uid
40 ms
sd
3 ms
pixel
12 ms
sd
3 ms
Pug
26 ms
sd
4 ms
sd
3 ms
container.html
5 ms
osd.js
25 ms
ad
72 ms
m_window_focus_non_hydra.js
8 ms
osd_listener.js
16 ms
gen_204
39 ms
time-traveler-quiz-which-word-came-first-4081-eaa237e33eb4bd475339b24c140889a6@1x.jpg
6 ms
594x396@1x.jpg
6 ms
594x396@1x.jpg
7 ms
express_html_inpage_rendering_lib_200_203.js
29 ms
abg.js
8 ms
d5qAyLYU.js
9 ms
pixel
28 ms
cookie_push.html
9 ms
9im3l02I.html
15 ms
pixel
31 ms
pixel
31 ms
T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js
5 ms
pixel
26 ms
sync
14 ms
index.html
6 ms
Enabler.js
11 ms
style.css
23 ms
jquery.min.js
32 ms
tweenmax_1.18.0_499ba64a23378545748ff12d372e59e9_min.js
28 ms
index.js
24 ms
tags.js
405 ms
glasses.png
6 ms
geico_logo.png
6 ms
cta.png
38 ms
subset-AachenStd-Bold.woff
6 ms
ifnotify
28 ms
bsredirect5.js
57 ms
dvtp_src.js
23 ms
ca
26 ms
bsredirect5_internal22.js
2 ms
bst2tv3.html
120 ms
verifyc.js
365 ms
dv-match4.js
7 ms
rum
19 ms
pixel
14 ms
img
49 ms
361047.gif
20 ms
pixel
12 ms
tags.js
660 ms
bsevent.gif
204 ms
a4bde6a98cb92777bc207e0c241317e6.gif
183 ms
dvtp_src_internal94.js
5 ms
dv-measurements44.js
6 ms
visit.js
438 ms
displayAd.js
80 ms
activeview
28 ms
j.ad
88 ms
event.gif
200 ms
avs691.js
3 ms
tf_adChoice11.js
176 ms
dcmads.js
3 ms
impl_v40.js
3 ms
B20019830.200385843;dc_ver=40.106;sz=728x90;osdl=1;u_sd=1;dc_adk=545834510;ord=mhzat4;click=https%3A%2F%2Fs.tribalfusion.com%2Fh.click%2FasmRRR1r7fUWbTnAbKnsrwpHvC5qBi2dmt5AFInFbZbYcYU1s3V0G7OmTfW2FZb2WUbBVmj2RE3XPVnNQtUO0HjpWAfn3VUU0FnDUAim5AQePmMC3HBnXWnIpW2u56YY5cv6UGY6UcnhSAQyTdYWWrZbY5U2wWEjoTTUlQqZbFRVJZcPbAnSd7cWcbW4rismHAoXaqO4tYZdSFftcyTLIo%2F;dc_rfl=1,https%3A%2F%2Fwww.merriam-webster.com%2F$0;xdt=0;crlt=')z0y_J_md;osda=2;sttr=7;prcl=s
114 ms
moatad.js
30 ms
p.media
86 ms
p.media
161 ms
p.media
232 ms
p.media
304 ms
p.media
368 ms
p.media
371 ms
p.media
373 ms
p.media
370 ms
p.media
375 ms
pixel.gif
48 ms
n.js
43 ms
1-Rgnl_a_Npm_LRG_NpmLRGBookDirect17_728x90-bu.jpg
13 ms
osd_listener.js
6 ms
pixel.gif
4 ms
activeview
29 ms
pixel
12 ms
i.match
379 ms
i.match
246 ms
Pix-1x1.gif
26 ms
i.match
315 ms
i.match
353 ms
i.match
355 ms
i.match
358 ms
tap.php
8 ms
pixel.gif
89 ms
pixel.gif
6 ms
pixel.gif
73 ms
tap.php
16 ms
img
26 ms
cksync.php
113 ms
Pug
23 ms
rum
29 ms
sd
14 ms
334886.png
56 ms
2948
115 ms
vendormm.gif
217 ms
sync
13 ms
cs
681 ms
732 ms
pixel
21 ms
4448
151 ms
match
130 ms
img
31 ms
img
27 ms
img
36 ms
img
30 ms
img
30 ms
bsmp.engine
298 ms
img
37 ms
pixel.gif
67 ms
match
12 ms
generic
6 ms
pixel
14 ms
bsevent.gif
9 ms
trpx.gif
78 ms
event.gif
9 ms
ad_choices_i_UR.png
3 ms
ad_choices_UR.png
3 ms
bsevent.gif
10 ms
event.gif
11 ms
pixel.gif
4 ms
img
17 ms
img
14 ms
img
37 ms
activity;src=2992003;pid=204621421;aid=404428648;ko=0;cid=73821235;rid=73700735;rv=1;met=1;×tamp=1504686259201;eid1=2;ecn1=1;etm1=10;eid2=871060;ecn2=1;etm2=0;
13 ms
pixel.gif
3 ms
i.word.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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
i.word.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
i.word.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I.word.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that I.word.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.
i.word.com
Open Graph data is detected on the main page of I Word. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: