Wiktionary.Org - Info wiktionary.org

wiktionary.org receives about 2,612,951 unique visitors and 5,069,125 (1.94 per visitor) page views per day which should earn about $22,737.15/day from advertising revenue. Estimated site value is $19,054,152.38. According to Alexa Traffic Rank wiktionary.org is ranked number 456 in the world and 0.154% of global Internet users visit it. Site is hosted in San Francisco, California, 94105, United States and links to network IP address 208.80.154.224. This server supports HTTPS and HTTP/2.

About - wiktionary.org

Collaborative project for creating a free lexical database in every language, complete with meanings, etymologies, and pronunciations.
How did wiktionary.org look in the past? Edit Site Info

wiktionary.org Profile

Title: Wiktionary
Keywords: wiktionary
Last update was 42 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with wiktionary.org in any way. Only publicly available statistics data are displayed.

How popular is wiktionary.org?

2.6M daily visitors
Daily Unique Visitors:
2,612,951
Monthly Unique Visitors:
78,388,530
Pages per Visit:
1.94
Daily Pageviews:
5,069,125
Alexa Rank:
456 visit alexa
Alexa Reach:
0.154%   (of global internet users)
Avg. visit duration:
05:17
Bounce rate:
77.76%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
18.28%
Referral:
19.49%
Search:
61.75%
Social:
0.48%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
United States 14.0%16.2%687
France 8.6%8.5%187
Germany 6.4%5.5%275
Russian Federation 5.2%5.1%450
China 5.1%4.7%1533
Poland 4.6%4.4%161
Greece 4.3%4.3%128
Japan 4.0%3.6%1034
United Kingdom 3.9%5.9%310
India 2.2%1.8%1974
Italy 2.2%2.6%553
Sweden 2.1%1.8%159
Korea, Republic of 1.9%1.5%669
Canada 1.8%1.6%601
Spain 1.7%2.0%646
Belgium 1.5%1.3%177
Finland 1.4%1.7%111
Czech Republic 1.4%1.4%198
Netherlands 1.3%1.2%273
Iran 1.2%0.9%1311
Australia 1.1%1.1%640
Norway 1.0%0.9%243
Azerbaijan 1.0%1.0%398
Austria 1.0%0.9%234
Switzerland 0.9%0.8%256
Brazil 0.9%0.9%1869
Mexico 0.9%0.8%1075
Viet Nam 0.8%0.9%455
Taiwan 0.8%0.5%1138
Ukraine 0.8%0.7%447
Romania 0.7%0.9%393
Hong Kong 0.6%0.8%569
Angola 0.6%0.3%1535
Indonesia 0.5%0.4%1598
Israel 0.5%0.5%337
Denmark 0.5%0.8%277
Thailand 0.5%0.6%814

Where do visitors go on this site?

Reach%Pageviews%PerUser
en.wiktionary.org
43.33%48.23%2.07
ru.wiktionary.org
14.58%12.79%1.63
fr.wiktionary.org
10.87%9.06%1.55
de.wiktionary.org
5.55%5.78%1.94
el.wiktionary.org
4.41%4.18%1.77
pl.wiktionary.org
3.85%3.56%1.72
es.wiktionary.org
2.75%1.89%1.3
zh.wiktionary.org
2.58%1.88%1.4
sv.wiktionary.org
1.47%1.10%1.4
ja.wiktionary.org
1.14%0.82%1.3
ko.wiktionary.org
1.10%0.80%1.4
pt.wiktionary.org
0.99%0.63%1.2
cs.wiktionary.org
0.97%0.88%1.7
wiktionary.org
0.92%0.49%1.0
nl.wiktionary.org
0.92%0.72%1.5
it.wiktionary.org
0.91%0.65%1.3
fi.wiktionary.org
0.82%0.78%1.8
vi.wiktionary.org
0.77%0.64%1.6
m.wiktionary.org
0.53%0.49%1.7
fa.wiktionary.org
0.52%0.38%1.4
tr.wiktionary.org
0.50%0.35%1.3
id.wiktionary.org
0.42%0.25%1.1
th.wiktionary.org
0.40%0.30%1.4
simple.wiktionary.org
0.40%0.30%1.4
no.wiktionary.org
0.39%0.26%1.2
ca.wiktionary.org
0.37%0.34%1.7
he.wiktionary.org
0.27%0.25%1.7
bg.wiktionary.org
0.25%0.18%1.3
ro.wiktionary.org
0.23%0.16%1.3
sr.wiktionary.org
0.22%0.18%1.5
ta.wiktionary.org
0.19%0.17%1.6
hu.wiktionary.org
0.16%0.13%1.6
uk.wiktionary.org
0.15%0.10%1.3
hy.wiktionary.org
0.14%0.10%1.3
ar.wiktionary.org
0.14%0.11%1.4
hi.wiktionary.org
0.11%0.18%3.1
az.wiktionary.org
0.10%0.08%1.5
lt.wiktionary.org
0.09%0.06%1.3
OTHER
0%0.75%0

Competitive Data

SEMrush
Domain:
  wiktionary.org
Rank:
(Rank based on keywords, cost and organic traffic)
  511
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  3,436,125
Organic Traffic:
(Number of visitors coming from top 20 search results)
  45,701,007
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $48,924,103.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

Data

Domain Authority:
  92
Page Authority:
  65
MozRank:
  7

How socially engaged is wiktionary.org?

Facebook:
  6
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
wiktionary.org
Last Change Time:
(The last time that the site changed status.)
2019-06-06 12:05:29
Region:
(The Ad Standard region to which this site has been assigned.)
B
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing


Mobile summary

Last Change Time:
(The last time that the site changed status.)
2019-06-06 12:05:29
Region:
(The Ad Standard region to which this site has been assigned.)
B
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing

Abusive Experience Report

Root domain:
wiktionary.org
Last Change Time:
(The last time that the site changed status.)
2019-06-06 12:05:29
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Passing

How much wiktionary.org can earn?

Daily Revenue:
$22,737.15
Monthly Revenue:
$682,114.50
Yearly Revenue:
$8,299,059.75
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 821,198$9,419.14
France 430,876$2,025.12
United Kingdom 299,078$1,863.26
Germany 278,802$1,346.61
China 238,249$736.19
Finland 86,175$624.77
Japan 182,489$583.96
Canada 81,106$568.55
Russian Federation 258,525$524.81
Sweden 91,244$485.42
Italy 131,797$459.97
Australia 55,760$419.88
Poland 223,042$403.71
Greece 217,972$392.35
Belgium 65,899$324.88
Netherlands 60,830$309.62
Switzerland 40,553$246.16
Norway 45,622$241.80
Korea, Republic of 76,037$176.41
Denmark 40,553$155.72
Czech Republic 70,968$154.00
Austria 45,622$148.27
Israel 25,346$148.02
India 91,244$145.99
Hong Kong 40,553$139.91
Spain 101,383$112.53
Azerbaijan 50,691$81.61
Brazil 45,622$80.75
Thailand 30,415$76.04
Romania 45,622$53.83
Iran 45,622$52.92
Ukraine 35,484$48.61
Taiwan 25,346$48.16
Angola 15,207$40.60
Mexico 40,553$39.34
Viet Nam 45,622$33.30
Indonesia 20,277$24.94

How much money do wiktionary.org lose due to Adblock?

Daily Revenue Loss:
$4,086.73
Monthly Revenue Loss:
$122,602.04
Yearly Revenue Loss:
$1,491,658.15
Daily Pageviews Blocked:
809,945
Monthly Pageviews Blocked:
24,298,344
Yearly Pageviews Blocked:
295,629,849
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 147,816$1,695.45
Germany 80,853$390.52
United Kingdom 47,853$298.12
France 47,396$222.76
Greece 85,009$153.02
Finland 19,820$143.70
Canada 20,277$142.14
Sweden 25,548$135.92
Poland 73,604$133.22
China 30,972$95.70
Australia 11,152$83.98
Italy 22,406$78.20
Netherlands 10,341$52.64
Norway 9,124$48.36
Switzerland 7,300$44.31
India 25,548$40.88
Belgium 7,908$38.99
Denmark 10,138$38.93
Austria 11,862$38.55
Russian Federation 15,512$31.49
Israel 4,816$28.12
Spain 19,263$21.38
Japan 5,475$17.52
Czech Republic 7,097$15.40
Indonesia 11,760$14.47
Hong Kong 4,055$13.99
Azerbaijan 8,111$13.06
Romania 9,581$11.31
Iran 7,300$8.47
Taiwan 4,055$7.71
Korea, Republic of 3,041$7.06
Ukraine 4,613$6.32
Brazil 2,737$4.85
Thailand 1,825$4.56
Mexico 3,650$3.54
Viet Nam 1,825$1.33
Angola 304$0.81

How much is wiktionary.org worth?

Website Value:
$19,054,152.38

Where is wiktionary.org hosted?

Server IP:
208.80.154.224
ASN:
AS14907 
ISP:
Wikimedia Foundation, Inc. 
Server Location:
San Francisco
California, CA
94105
United States, US
 

Other sites hosted on 208.80.154.224

How fast does wiktionary.org load?

Average Load Time:
(736 ms) 89 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)3.5s 44% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 44% 38% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 38% 16% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 16%
First Input Delay (FID)72ms 93% of loads for this page have a fast (<50ms) First Input Delay (FID) 93% 5% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 5% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)3.5s 44% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 44% 38% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 38% 16% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 16%
First Input Delay (FID)72ms 93% of loads for this page have a fast (<50ms) First Input Delay (FID) 93% 5% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 5% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 554 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
554
Maximum DOM Depth
6
Maximum Child Elements
42
Avoid multiple page redirects - Potential savings of 340 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://wiktionary.org/)
0
https://wiktionary.org/
190
https://www.wiktionary.org/
150
Keep request counts low and transfer sizes small - 23 requests • 118 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
23118 KB
Image
18102 KB
Document
18 KB
Script
13 KB
Stylesheet
13 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
19105 KB
Eliminate render-blocking resources - Potential savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*
3 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://wiktionary.org/
0 ms29 ms0 KB0 KB301
https://wiktionary.org/
30 ms186 ms1 KB0 KB301text/html
https://www.wiktionary.org/
186 ms236 ms8 KB30 KB200text/htmlDocument
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*
251 ms321 ms3 KB6 KB200text/cssStylesheet
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=scripts&skin=vector&*
251 ms321 ms3 KB7 KB200text/javascriptScript
https://upload.wikimedia.org/wikipedia/meta/thumb/7/7e/Vector_search_icon.svg/12px-Vector_search_icon.svg.png
251 ms321 ms1 KB0 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/9/9b/Wikipedia-logo_sister_1x.png
254 ms321 ms4 KB3 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/a/aa/Wikinews-logo_sister_1x.png
255 ms322 ms3 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/c/c8/Wikiquote-logo_sister_1x.png
255 ms322 ms2 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/7/74/Wikibooks-logo_sister_1x.png
255 ms322 ms3 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/0/00/Wikidata-logo_sister_1x.png
255 ms323 ms1 KB0 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/8/8c/Wikispecies-logo_sister_1x.png
255 ms323 ms3 KB3 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/2/27/Wikisource-logo_sister_1x.png
256 ms323 ms3 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/a/af/Wikiversity-logo_sister_1x.png
256 ms324 ms2 KB1 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/7/74/Wikivoyage-logo_sister_1x.png
256 ms324 ms2 KB1 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/9/90/Commons-logo_sister_1x.png
256 ms325 ms2 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/1/16/MediaWiki-logo_sister_1x.png
256 ms325 ms8 KB7 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/f/f2/Meta-logo_sister_1x.png
256 ms330 ms3 KB2 KB200image/pngImage
https://www.wiktionary.org/static/images/wikimedia-button.png
256 ms332 ms3 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/2/21/Wiktionary-logo-tiles_1x.png
266 ms332 ms34 KB33 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/f/ff/Wiktionary-logo-en_1x.png
266 ms340 ms12 KB11 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/1/19/Wiktionary_book_logo_1x.png
267 ms340 ms14 KB14 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/commons/b/bd/Bookshelf-40x201_6.png
485 ms569 ms1 KB0 KB200image/pngImage
Serve static assets with an efficient cache policy - 19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://upload.wikimedia.org/wikipedia/meta/2/21/Wiktionary-logo-tiles_1x.png
0 ms34 KB
https://upload.wikimedia.org/wikipedia/meta/1/19/Wiktionary_book_logo_1x.png
0 ms14 KB
https://upload.wikimedia.org/wikipedia/meta/f/ff/Wiktionary-logo-en_1x.png
0 ms12 KB
https://upload.wikimedia.org/wikipedia/meta/1/16/MediaWiki-logo_sister_1x.png
0 ms8 KB
https://upload.wikimedia.org/wikipedia/meta/9/9b/Wikipedia-logo_sister_1x.png
0 ms4 KB
https://upload.wikimedia.org/wikipedia/meta/8/8c/Wikispecies-logo_sister_1x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/a/aa/Wikinews-logo_sister_1x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/2/27/Wikisource-logo_sister_1x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/7/74/Wikibooks-logo_sister_1x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/f/f2/Meta-logo_sister_1x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/9/90/Commons-logo_sister_1x.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/meta/c/c8/Wikiquote-logo_sister_1x.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/meta/a/af/Wikiversity-logo_sister_1x.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/meta/7/74/Wikivoyage-logo_sister_1x.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/commons/b/bd/Bookshelf-40x201_6.png
0 ms1 KB
https://upload.wikimedia.org/wikipedia/meta/thumb/7/7e/Vector_search_icon.svg/12px-Vector_search_icon.svg.png
0 ms1 KB
https://upload.wikimedia.org/wikipedia/meta/0/00/Wikidata-logo_sister_1x.png
0 ms1 KB
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=scripts&skin=vector&*
300000 ms3 KB
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*
300000 ms3 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
274 ms
8 ms
286 ms
13 ms
299 ms
16 ms
316 ms
185 ms
516 ms
64 ms
604 ms
16 ms
621 ms
7 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
334 ms5 ms1 ms
Avoids enormous network payloads - Total size was 118 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://upload.wikimedia.org/wikipedia/meta/2/21/Wiktionary-logo-tiles_1x.png
34 KB
https://upload.wikimedia.org/wikipedia/meta/1/19/Wiktionary_book_logo_1x.png
14 KB
https://upload.wikimedia.org/wikipedia/meta/f/ff/Wiktionary-logo-en_1x.png
12 KB
https://www.wiktionary.org/
8 KB
https://upload.wikimedia.org/wikipedia/meta/1/16/MediaWiki-logo_sister_1x.png
8 KB
https://upload.wikimedia.org/wikipedia/meta/9/9b/Wikipedia-logo_sister_1x.png
4 KB
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=scripts&skin=vector&*
3 KB
https://upload.wikimedia.org/wikipedia/meta/8/8c/Wikispecies-logo_sister_1x.png
3 KB
https://upload.wikimedia.org/wikipedia/meta/a/aa/Wikinews-logo_sister_1x.png
3 KB
https://www.wiktionary.org/static/images/wikimedia-button.png
3 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
262 ms
Other
35 ms
Rendering
17 ms
Parse HTML & CSS
13 ms
Script Evaluation
12 ms
Script Parsing & Compilation
2 ms
Serve images in next-gen formats - Potential savings of 18 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://upload.wikimedia.org/wikipedia/meta/2/21/Wiktionary-logo-tiles_1x.png
33 KB18 KB
Minimize Critical Requests Depth - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 50 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

94
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)2.7s 44% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 43% 44% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 44% 12% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 12%
First Input Delay (FID)46ms 95% of loads for this page have a fast (<50ms) First Input Delay (FID) 95% 3% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)2.7s 43% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 43% 44% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 44% 12% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 12%
First Input Delay (FID)46ms 93% of loads for this page have a fast (<50ms) First Input Delay (FID) 95% 3% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 5220 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 554 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
554
Maximum DOM Depth
6
Maximum Child Elements
42
Avoid multiple page redirects - Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://wiktionary.org/)
0
https://wiktionary.org/
630
https://www.wiktionary.org/
480
Keep request counts low and transfer sizes small - 23 requests • 242 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
23242 KB
Image
18226 KB
Document
18 KB
Script
13 KB
Stylesheet
13 KB
Other
21 KB
Media
00 KB
Font
00 KB
Third-party
20232 KB
Eliminate render-blocking resources - Potential savings of 780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*
3 KB780
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://wiktionary.org/
0 ms33 ms0 KB0 KB301
https://wiktionary.org/
35 ms92 ms1 KB0 KB301text/html
https://www.wiktionary.org/
93 ms149 ms8 KB30 KB200text/htmlDocument
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*
163 ms230 ms3 KB6 KB200text/cssStylesheet
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=scripts&skin=vector&*
164 ms231 ms3 KB7 KB200text/javascriptScript
https://upload.wikimedia.org/wikipedia/meta/thumb/7/7e/Vector_search_icon.svg/24px-Vector_search_icon.svg.png
164 ms231 ms2 KB1 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikipedia-logo_sister_2x.png
166 ms231 ms9 KB8 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikinews-logo_sister_2x.png
167 ms232 ms7 KB6 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/9/97/Wikiquote-logo_sister_2x.png
167 ms232 ms3 KB3 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/0/0f/Wikibooks-logo_sister_2x.png
167 ms232 ms4 KB3 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/e/ec/Wikidata-logo_sister_2x.png
167 ms233 ms1 KB0 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/7/7d/Wikispecies-logo_sister_2x.png
167 ms233 ms7 KB6 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/a/a4/Wikisource-logo_sister_2x.png
168 ms233 ms5 KB4 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/6/69/Wikiversity-logo_sister_2x.png
168 ms234 ms3 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/4/4e/Wikivoyage-logo_sister_2x.png
168 ms237 ms2 KB2 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/b/b6/Commons-logo_sister_2x.png
168 ms237 ms4 KB3 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/2/2e/MediaWiki-logo_sister_2x.png
168 ms237 ms16 KB15 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/a/ac/Meta-logo_sister_2x.png
168 ms238 ms4 KB3 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/b/b7/A_Wikimedia_project_2x.png
168 ms251 ms6 KB5 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/3/30/Wiktionary-logo-tiles_2x.png
175 ms254 ms80 KB80 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/e/eb/Wiktionary-logo-en_2x.png
176 ms255 ms24 KB23 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/d/df/Wiktionary_book_logo_2x.png
176 ms258 ms47 KB46 KB200image/pngImage
https://upload.wikimedia.org/wikipedia/meta/4/46/Bookshelf-40x20_2x.png
325 ms413 ms2 KB1 KB200image/pngImage
Serve static assets with an efficient cache policy - 20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://upload.wikimedia.org/wikipedia/meta/3/30/Wiktionary-logo-tiles_2x.png
0 ms80 KB
https://upload.wikimedia.org/wikipedia/meta/d/df/Wiktionary_book_logo_2x.png
0 ms47 KB
https://upload.wikimedia.org/wikipedia/meta/e/eb/Wiktionary-logo-en_2x.png
0 ms24 KB
https://upload.wikimedia.org/wikipedia/meta/2/2e/MediaWiki-logo_sister_2x.png
0 ms16 KB
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikipedia-logo_sister_2x.png
0 ms9 KB
https://upload.wikimedia.org/wikipedia/meta/7/7d/Wikispecies-logo_sister_2x.png
0 ms7 KB
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikinews-logo_sister_2x.png
0 ms7 KB
https://upload.wikimedia.org/wikipedia/meta/b/b7/A_Wikimedia_project_2x.png
0 ms6 KB
https://upload.wikimedia.org/wikipedia/meta/a/a4/Wikisource-logo_sister_2x.png
0 ms5 KB
https://upload.wikimedia.org/wikipedia/meta/a/ac/Meta-logo_sister_2x.png
0 ms4 KB
https://upload.wikimedia.org/wikipedia/meta/0/0f/Wikibooks-logo_sister_2x.png
0 ms4 KB
https://upload.wikimedia.org/wikipedia/meta/b/b6/Commons-logo_sister_2x.png
0 ms4 KB
https://upload.wikimedia.org/wikipedia/meta/9/97/Wikiquote-logo_sister_2x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/6/69/Wikiversity-logo_sister_2x.png
0 ms3 KB
https://upload.wikimedia.org/wikipedia/meta/4/4e/Wikivoyage-logo_sister_2x.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/meta/4/46/Bookshelf-40x20_2x.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/meta/thumb/7/7e/Vector_search_icon.svg/24px-Vector_search_icon.svg.png
0 ms2 KB
https://upload.wikimedia.org/wikipedia/meta/e/ec/Wikidata-logo_sister_2x.png
0 ms1 KB
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=scripts&skin=vector&*
300000 ms3 KB
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*
300000 ms3 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
177 ms
9 ms
189 ms
10 ms
200 ms
14 ms
215 ms
118 ms
347 ms
67 ms
417 ms
19 ms
440 ms
9 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
1080 ms18 ms4 ms
Avoids enormous network payloads - Total size was 242 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://upload.wikimedia.org/wikipedia/meta/3/30/Wiktionary-logo-tiles_2x.png
80 KB
https://upload.wikimedia.org/wikipedia/meta/d/df/Wiktionary_book_logo_2x.png
47 KB
https://upload.wikimedia.org/wikipedia/meta/e/eb/Wiktionary-logo-en_2x.png
24 KB
https://upload.wikimedia.org/wikipedia/meta/2/2e/MediaWiki-logo_sister_2x.png
16 KB
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikipedia-logo_sister_2x.png
9 KB
https://www.wiktionary.org/
8 KB
https://upload.wikimedia.org/wikipedia/meta/7/7d/Wikispecies-logo_sister_2x.png
7 KB
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikinews-logo_sister_2x.png
7 KB
https://upload.wikimedia.org/wikipedia/meta/b/b7/A_Wikimedia_project_2x.png
6 KB
https://upload.wikimedia.org/wikipedia/meta/a/a4/Wikisource-logo_sister_2x.png
5 KB
Minimizes main-thread work - 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
761 ms
Other
136 ms
Rendering
123 ms
Script Evaluation
43 ms
Parse HTML & CSS
39 ms
Script Parsing & Compilation
7 ms
Serve images in next-gen formats - Potential savings of 83 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://upload.wikimedia.org/wikipedia/meta/3/30/Wiktionary-logo-tiles_2x.png
80 KB44 KB
https://upload.wikimedia.org/wikipedia/meta/d/df/Wiktionary_book_logo_2x.png
46 KB28 KB
https://upload.wikimedia.org/wikipedia/meta/2/2e/MediaWiki-logo_sister_2x.png
15 KB11 KB
Minimize Critical Requests Depth - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 60 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://wiktionary.org/
https://wiktionary.org/
https://www.wiktionary.org/

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&*

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="//ca.wiktionary.org/">Català</a> and 149 others are close to other tap targets .
The tap target <a href="//ku.wiktionary.org/">Kurdî / كوردی</a> and 12 others are close to other tap targets .

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://upload.wikimedia.org/wikipedia/meta/0/0f/Wikibooks-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/2/2e/MediaWiki-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/3/30/Wiktionary-logo-tiles_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/4/46/Bookshelf-40x20_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikinews-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/4/4b/Wikipedia-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/4/4e/Wikivoyage-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/6/***/Wikiversity-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/7/7d/Wikispecies-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/9/97/Wikiquote-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/a/a4/Wikisource-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/a/ac/Meta-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/b/b6/Commons-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/b/b7/A_Wikimedia_project_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/d/df/Wiktionary_book_logo_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/e/eb/Wiktionary-logo-en_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/e/ec/Wikidata-logo_sister_2x.png (expiration not specified)
https://upload.wikimedia.org/wikipedia/meta/thumb/7/7e/Vector_search_icon.svg/24px-Vector_search_icon.svg.png (expiration not specified)
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=scripts&skin=vector&* (5 minutes)
https://meta.wikimedia.org/w/load.php?debug=false&lang=en&modules=ext.gadget.wm-portal&only=styles&skin=vector&* (5 minutes)

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 621B (28% reduction).

Compressing https://upload.wikimedia.org/wikipedia/meta/4/4e/Wikivoyage-logo_sister_2x.png could save 321B (21% reduction).
Compressing https://upload.wikimedia.org/wikipedia/meta/thumb/7/7e/Vector_search_icon.svg/24px-Vector_search_icon.svg.png could save 300B (41% reduction).
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

Does wiktionary.org use compression?

wiktionary.org use gzip compression.
Original size: 30 KB
Compressed size: 7.1 KB
File reduced by: 22.9 KB (76%)

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  94
Vendor reliability:
  94
Privacy:
  94
Child safety:
  93

SSL Checker - SSL Certificate Verify

wiktionary.org supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.wikipedia.org
Organization: Wikimedia Foundation, Inc.
Location: San Francisco, California, US
Issuer: GlobalSign Organization Validation CA - SHA256 - G2
Valid from: Nov 8 21:21:04 2018 GMT
Valid until: Nov 22 07:59:59 2019 GMT
Authority: Is not a CA
Keysize:
Common Name: GlobalSign Organization Validation CA - SHA256 - G2
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Aug 2 10:00:00 2011 GMT
Valid until: Aug 2 10:00:00 2022 GMT
Authority: Is a CA
Keysize: 2048 Bits

Verify HTTP/2 Support

wiktionary.org supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

Http Header

Date: Sat, 08 Jun 2019 11:36:14 GMT
Server: Varnish
X-Varnish: 821110189
X-Cache: cp1083 int
X-Cache-Status: int-front
Server-Timing: cache;desc="int-front"
Set-Cookie: WMF-Last-Access=08-Jun-2019;Path=/;HttpOnly;secure;Expires=Wed, 10 Jul 2019 00:00:00 GMT
Set-Cookie: WMF-Last-Access-Global=08-Jun-2019;Path=/;Domain=.wiktionary.org;HttpOnly;secure;Expires=Wed, 10 Jul 2019 00:00:00 GMT
X-Client-IP: 67.212.187.106
Location: https://wiktionary.org/
Content-Length: 0
Connection: keep-alive

HTTP/2 301 
date: Sat, 08 Jun 2019 11:36:14 GMT
content-type: text/html; charset=iso-8859-1
content-length: 235
location: https://www.wiktionary.org/
server: mw1263.eqiad.wmnet
cache-control: max-age=2592000
expires: Sun, 07 Jul 2019 09:58:27 GMT
vary: X-Seven,X-Forwarded-Proto
x-varnish: 564818752 146055084, 121166656 634951242
via: 1.1 varnish (Varnish/5.1), 1.1 varnish (Varnish/5.1)
age: 92266
x-cache: cp1079 hit/6, cp1085 hit/260
x-cache-status: hit-front
server-timing: cache;desc="hit-front"
strict-transport-security: max-age=106384710; includeSubDomains; preload
set-cookie: WMF-Last-Access=08-Jun-2019;Path=/;HttpOnly;secure;Expires=Wed, 10 Jul 2019 00:00:00 GMT
set-cookie: WMF-Last-Access-Global=08-Jun-2019;Path=/;Domain=.wiktionary.org;HttpOnly;secure;Expires=Wed, 10 Jul 2019 00:00:00 GMT
x-analytics: https=1;nocookies=1
x-client-ip: 67.212.187.106
set-cookie: GeoIP=US:CA:Novato:38.10:-122.59:v4; Path=/; secure; Domain=.wiktionary.org

HTTP/2 200 
date: Sat, 08 Jun 2019 11:36:15 GMT
content-type: text/html
content-length: 7273
server: mw1261.eqiad.wmnet
cache-control: s-maxage=86400, must-revalidate, max-age=3600
etag: W/"7804-5868f511ff85f"
last-modified: Mon, 15 Apr 2019 10:43:03 GMT
backend-timing: D=206 t=1559812018898458
content-encoding: gzip
vary: X-Seven, Accept-Encoding
x-varnish: 1046251710 944688416, 128237907 60350601
via: 1.1 varnish (Varnish/5.1), 1.1 varnish (Varnish/5.1)
age: 14724
x-cache: cp1079 hit/10, cp1085 hit/79
x-cache-status: hit-front
server-timing: cache;desc="hit-front"
strict-transport-security: max-age=106384710; includeSubDomains; preload
set-cookie: WMF-Last-Access=08-Jun-2019;Path=/;HttpOnly;secure;Expires=Wed, 10 Jul 2019 00:00:00 GMT
set-cookie: WMF-Last-Access-Global=08-Jun-2019;Path=/;Domain=.wiktionary.org;HttpOnly;secure;Expires=Wed, 10 Jul 2019 00:00:00 GMT
x-analytics: https=1;nocookies=1
x-client-ip: 67.212.187.106
set-cookie: GeoIP=US:CA:Novato:38.10:-122.59:v4; Path=/; secure; Domain=.wiktionary.org
accept-ranges: bytes

DNS Lookup

Type Ip Target TTL
HINFO 3600
NS ns1.wikimedia.org 3578
NS ns0.wikimedia.org 3578
NS ns2.wikimedia.org 3578

Whois Lookup

Domain Created:
2002-12-14
Domain Age:
16 years 5 months 25 days  
WhoIs:
 

whois lookup at whois.pir.org...
Domain Name: WIKTIONARY.ORG
Registry Domain ID: D93120700-LROR
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2012-05-09T00:25:42Z
Creation Date: 2002-12-14T10:42:51Z
Registry Expiry Date: 2021-12-14T10:42:50Z
Registrar Registration Expiration Date:
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.2083895740
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: Wikimedia Foundation, Inc.
Registrant State/Province: CA
Registrant Country: US
Name Server: NS0.WIKIMEDIA.ORG
Name Server: NS1.WIKIMEDIA.ORG
Name Server: NS2.WIKIMEDIA.ORG
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2019-06-08T11:35:35Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 42 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with wiktionary.org in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

qualitycleaningphilly.com
1 secs
sehrayin.com
3 secs
twitch.ren
4 secs
swipewizard.com
5 secs
vinnythevoice.com
7 secs
dsgvertiv.com
10 secs
daiyun-vip.com
11 secs
evergreencurrent.com
14 secs
beholdman.com
14 secs
boujeeboardshop.com
15 secs

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
wiktionary.org widget