eyny.com

eyny.com is SSL secured

Free website and domain report on eyny.com

Last Updated: 16th September, 2023 Update Now
Overview

Snoop Summary for eyny.com

This is a free and comprehensive report about eyny.com. Eyny.com is hosted in United States on a server with an IP address of 169.60.163.103, where USD is the local currency and the local language is English. Our records indicate that eyny.com is privately registered by Whois Privacy Protection Service, Inc.. Eyny.com is expected to earn an estimated $15,432 USD per day from advertising revenue. The sale of eyny.com would possibly be worth $11,265,040 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Eyny.com is unbelievably popular with an estimated 1,657,369 daily unique visitors. This report was last updated 16th September, 2023.

About eyny.com

Site Preview: eyny.com eyny.com
Title: 伊莉心情車站
Description: 熱門話題、消閒娛樂、學術電腦、資訊交流等討論區。
Keywords and Tags: bulletin boards, eyny, eyny com, eyny video, eyny 影片, forum, popular, www eyny com, 伊 莉 影片, 伊 莉 影片 區, 伊 莉 討論, 伊 莉 討論 區, 伊利 影片, 依 例 討論 區, 依 例 論壇
Related Terms:
Fav Icon:
Age: Over 20 years old
Domain Created: 29th August, 2003
Domain Updated: 6th June, 2022
Domain Expires: 29th August, 2025
Review

Snoop Score

5/5 (Perfect!)

Valuation

$11,265,040 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,619
Alexa Reach: 0.0213%
SEMrush Rank (US): 151,079
SEMrush Authority Score: 68
Moz Domain Authority: 44
Moz Page Authority: 52

Rank By Country

Country Alexa Rank
Australia Flag Australia 3,472
Canada Flag Canada 3,865
China Flag China 4,856
Hong Kong Flag Hong Kong 156
Japan Flag Japan 5,357
Korea Republic Of Flag Korea Republic Of 2,771
Malaysia Flag Malaysia 2,076
Singapore Flag Singapore 1,645
Taiwan, Province Of China Flag Taiwan, Province Of China 39
United States Flag United States 13,790

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 5,884 0
Traffic: 10,677 0
Cost: $1 USD $0 USD
Traffic

Visitors

Daily Visitors: 1,657,369
Monthly Visitors: 50,445,095
Yearly Visitors: 604,939,730
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Australia Flag Australia Daily: 13,259
Monthly: 403,561
Yearly: 4,839,518
0.8%
Canada Flag Canada Daily: 13,259
Monthly: 403,561
Yearly: 4,839,518
0.8%
China Flag China Daily: 109,386
Monthly: 3,329,376
Yearly: 39,926,022
6.6%
Hong Kong Flag Hong Kong Daily: 145,848
Monthly: 4,439,168
Yearly: 53,234,696
8.8%
Japan Flag Japan Daily: 31,490
Monthly: 958,457
Yearly: 11,493,855
1.9%
Korea Republic Of Flag Korea Republic Of Daily: 36,462
Monthly: 1,109,792
Yearly: 13,308,674
2.2%
Malaysia Flag Malaysia Daily: 13,259
Monthly: 403,561
Yearly: 4,839,518
0.8%
Other Daily: 46,406
Monthly: 1,412,463
Yearly: 16,938,312
2.8%
Singapore Flag Singapore Daily: 8,287
Monthly: 252,225
Yearly: 3,024,699
0.5%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: 1,199,935
Monthly: 36,522,249
Yearly: 437,976,364
72.4%
United States Flag United States Daily: 39,777
Monthly: 1,210,682
Yearly: 14,518,554
2.4%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $15,432 USD
Monthly Revenue: $469,688 USD
Yearly Revenue: $5,632,515 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Australia Flag Australia Daily: $207 USD
Monthly: $6,309 USD
Yearly: $75,656 USD
1.3%
Canada Flag Canada Daily: $307 USD
Monthly: $9,338 USD
Yearly: $111,983 USD
2%
China Flag China Daily: $1,483 USD
Monthly: $45,147 USD
Yearly: $541,402 USD
9.6%
Hong Kong Flag Hong Kong Daily: $245 USD
Monthly: $7,457 USD
Yearly: $89,425 USD
1.6%
Japan Flag Japan Daily: $204 USD
Monthly: $6,204 USD
Yearly: $74,394 USD
1.3%
Korea Republic Of Flag Korea Republic Of Daily: $415 USD
Monthly: $12,641 USD
Yearly: $151,589 USD
2.7%
Malaysia Flag Malaysia Daily: $64 USD
Monthly: $1,933 USD
Yearly: $23,185 USD
0.4%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Singapore Flag Singapore Daily: $22 USD
Monthly: $668 USD
Yearly: $8,014 USD
0.1%
Taiwan, Province Of China Flag Taiwan, Province Of China Daily: $1,303 USD
Monthly: $39,654 USD
Yearly: $475,532 USD
8.4%
United States Flag United States Daily: $11,182 USD
Monthly: $340,337 USD
Yearly: $4,081,335 USD
72.5%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 213,769,288
Referring Domains: 3,888
Referring IPs: 2,978
Eyny.com has 213,769,288 backlinks according to SEMrush. 100% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve eyny.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of eyny.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: http://www.wahas.com/thread-552601-1-1.html
Target: https://video.eyny.com/

2
Source: http://www.wahas.com/thread-552601-1-1.html
Target: http://blog.eyny.com/

3
Source: http://www.wahas.com/thread-755358-1-1.html
Target: https://video.eyny.com/

4
Source: http://www.wahas.com/thread-671814-1-1.html
Target: https://video.eyny.com/

5
Source: http://www.wahas.com/thread-478972-1-1.html
Target: https://www.eyny.com/

Top Ranking Keywords (US)

1
Keyword: eyny
Ranked Page: https://www.eyny.com/store.php?uid=0&rd=1

2
Keyword: eyny
Ranked Page: https://video.eyny.com/video.php?mod=user&uid=15940870

3
Keyword: 伊 莉 影片
Ranked Page: https://video.eyny.com/channel/UCfHIcUN2xn/charts

4
Keyword: eyny com
Ranked Page: https://www.eyny.com/

5
Keyword: 伊 莉 討論 區
Ranked Page: https://www.eyny.com/

Domain Analysis

Value Length
Domain: eyny.com 8
Domain Name: eyny 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.37 seconds
Load Time Comparison: Faster than 56% of sites

PageSpeed Insights

Avg. (All Categories) 67
Performance 95
Accessibility 85
Best Practices 83
SEO 73
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www06.eyny.com/member.php
Updated: 30th October, 2022

0.47 seconds
First Contentful Paint (FCP)
98%
1%
1%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
95

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for eyny.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.7 s
The time taken for the page to become fully interactive.
Total Blocking Time — 20 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://eyny.com/
http/1.1
0
251.48900004569
251
0
302
text/html
http://www06.eyny.com/
http/1.1
251.79500004742
964.28399998695
1041
0
302
text/html
http://www06.eyny.com/member.php?mod=logging&action=login
http/1.1
964.72699998412
1375.6460000295
6496
15327
200
text/html
Document
http://www06.eyny.com/data/cache/style_1_common.css?qbh
http/1.1
1381.2910000561
1638.951000059
12903
55698
200
text/css
Stylesheet
http://www06.eyny.com/data/cache/css_common.css?qbh
http/1.1
1381.3770000124
1513.6870000279
2302
7195
200
text/css
Stylesheet
http://www06.eyny.com/data/cache/js_common.js?qbh
http/1.1
1381.585999974
1617.7540000062
2721
6728
200
text/javascript
Script
http://www06.eyny.com/data/cache/js_show_ads.js?qbh
http/1.1
1381.7549999803
1499.0430000471
665
514
200
text/javascript
Script
http://www06.eyny.com/data/cache/common.js?qbh
http/1.1
1381.9030000595
1741.7000000132
16950
55867
200
text/javascript
Script
http://www06.eyny.com/static/image/common/logo.gif
http/1.1
1750.7270000642
2004.6040000161
6739
6453
200
image/gif
Image
https://www.google.com/recaptcha/api.js?render=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW
h2
1640.2529999614
1647.9040000122
1179
884
200
text/javascript
Script
http://www06.eyny.com/data/cache/md5.js?qbh
http/1.1
1649.2449999787
1789.0510000288
1828
4730
200
text/javascript
Script
http://www06.eyny.com/home.php?mod=misc&ac=sendmail&rand=1667143218
http/1.1
1745.8300000289
1913.2920000702
942
0
200
text/html
Script
http://www06.eyny.com/data/cache/js_langconv.js?qbh
http/1.1
1750.5880000535
2004.8289999831
7552
10409
200
text/javascript
Script
http://www06.eyny.com/ads&channel=1&format=728x90&type=image&border=0&ajax=1
http/1.1
1751.5689999564
2101.798000047
894
0
302
text/html
http://www06.eyny.com/static/image/common/qmenu.png
http/1.1
1754.402999999
1872.3669999745
2030
1744
200
image/png
Image
http://www06.eyny.com/static/image/common/search.png
http/1.1
1754.9850000069
1985.7240000274
3219
2934
200
image/png
Image
http://www06.eyny.com/static/image/common/arrwd.gif
http/1.1
1755.4660000606
2004.3010000372
335
51
200
image/gif
Image
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
h2
1817.8110000445
1831.1840000097
162405
406468
200
text/javascript
Script
http://www06.eyny.com/static/image/common/px.png
http/1.1
1820.2730000485
1954.7050000401
495
210
200
image/png
Image
http://www06.eyny.com/static/image/common/pn.png
http/1.1
1821.0070000496
2078.913000063
877
592
200
image/png
Image
http://www06.eyny.com/static/image/common/scrolltop.png
http/1.1
1917.2320000362
2035.2519999724
1354
1068
200
image/png
Image
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA2LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=lim2fcmvxlou
h2
2029.1229999857
2063.0890000612
22894
42493
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/styles__ltr.css
h2
2072.6060000015
2081.3440000638
25184
52913
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
h2
2072.9079999728
2083.357000025
162405
406468
200
text/javascript
Script
http://www06.eyny.com/member.php?mod=logging&action=login
http/1.1
2102.0799999824
2276.2230000226
6400
15226
200
text/html
XHR
https://www.gstatic.com/recaptcha/api2/logo_48.png
h2
2174.8910000315
2179.1460000677
3101
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
2175.5750000011
2178.7880000193
11676
10748
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
2175.7069999585
2178.489999962
11716
10788
200
font/woff2
Font
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=NJPGLzpIZgjszqyOymHUP0XR
h2
2186.6830000654
2194.0709999762
832
102
200
text/javascript
Other
https://www.google.com/recaptcha/api2/reload?k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW
h2
2428.9470000658
2491.5690000635
19183
32205
200
application/json
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1379.302
9.482
1753.585
63.36
1819.68
45.682
1867.463
6.15
1873.666
10.921
1894.336
19.801
2011.451
19.666
2066.653
7.364
2112.237
19.806
2132.068
47.626
2187.584
15.171
2202.809
16.198
2224.756
45.566
2273.264
7.184
2282.303
28.199
2311.387
80.356
2392.012
5.967
2493.374
5.371
2498.803
21.866
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Eyny.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Eyny.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Eyny.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Eyny.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 34 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Eyny.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/styles__ltr.css
25184
23699
http://www06.eyny.com/data/cache/style_1_common.css?qbh
12903
11607
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 410 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www06.eyny.com/member.php?mod=logging&action=login
411.914
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Eyny.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image — Potential savings of 70 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://www06.eyny.com/static/image/common/search.png
70
Avoids enormous network payloads — Total size was 485 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
162405
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
162405
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/styles__ltr.css
25184
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA2LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=lim2fcmvxlou
22894
https://www.google.com/recaptcha/api2/reload?k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW
19183
http://www06.eyny.com/data/cache/common.js?qbh
16950
http://www06.eyny.com/data/cache/style_1_common.css?qbh
12903
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
11716
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11676
http://www06.eyny.com/data/cache/js_langconv.js?qbh
7552
Uses efficient cache policy on static assets — 15 resources found
Eyny.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/api2/logo_48.png
604800000
3101
http://www06.eyny.com/data/cache/common.js?qbh
1209600000
16950
http://www06.eyny.com/data/cache/style_1_common.css?qbh
1209600000
12903
http://www06.eyny.com/data/cache/js_langconv.js?qbh
1209600000
7552
http://www06.eyny.com/static/image/common/logo.gif
1209600000
6739
http://www06.eyny.com/static/image/common/search.png
1209600000
3219
http://www06.eyny.com/data/cache/js_common.js?qbh
1209600000
2721
http://www06.eyny.com/data/cache/css_common.css?qbh
1209600000
2302
http://www06.eyny.com/static/image/common/qmenu.png
1209600000
2030
http://www06.eyny.com/data/cache/md5.js?qbh
1209600000
1828
http://www06.eyny.com/static/image/common/scrolltop.png
1209600000
1354
http://www06.eyny.com/static/image/common/pn.png
1209600000
877
http://www06.eyny.com/data/cache/js_show_ads.js?qbh
1209600000
665
http://www06.eyny.com/static/image/common/px.png
1209600000
495
http://www06.eyny.com/static/image/common/arrwd.gif
1209600000
335
Avoids an excessive DOM size — 279 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
279
Maximum DOM Depth
18
Maximum Child Elements
13
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Eyny.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
283.897
249.481
14.383
http://www06.eyny.com/member.php?mod=logging&action=login
160.251
9.761
1.838
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA2LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=lim2fcmvxlou
74.83
60.98
1.835
Minimizes main-thread work — 0.6 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
326.864
Style & Layout
125.811
Other
59.503
Script Parsing & Compilation
19.601
Rendering
17.325
Parse HTML & CSS
9.91
Garbage Collection
7.34
Keep request counts low and transfer sizes small — 30 requests • 485 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
30
496569
Script
9
356647
Stylesheet
3
40389
Document
2
29390
Other
6
28601
Font
2
23392
Image
8
18150
Media
0
0
Third-party
10
420575
Minimize third-party usage — Third-party code blocked the main thread for 20 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
353095
24.693
44088
0
23392
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
1766
80
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 1.6 s
The time taken for the page contents to be visibly populated.

Other

Eliminate render-blocking resources — Potential savings of 360 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Eyny.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www06.eyny.com/data/cache/style_1_common.css?qbh
12903
110
http://www06.eyny.com/data/cache/css_common.css?qbh
2302
110
http://www06.eyny.com/data/cache/js_common.js?qbh
2721
110
http://www06.eyny.com/data/cache/js_show_ads.js?qbh
665
110
http://www06.eyny.com/data/cache/common.js?qbh
16950
150
Reduce unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
162405
75574

Other

Avoid multiple page redirects — Potential savings of 1,610 ms
Redirects can cause additional delays before the page can begin loading. Eyny.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://eyny.com/
190
http://www06.eyny.com/
1420
http://www06.eyny.com/member.php?mod=logging&action=login
0
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.2130000181496
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
2.7830000035465
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://www06.eyny.com/static/image/common/logo.gif
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of eyny.com on mobile screens.
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of eyny.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Eyny.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Navigation

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that eyny.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 19 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://eyny.com/
Allowed
http://www06.eyny.com/
Allowed
http://www06.eyny.com/member.php?mod=logging&action=login
Allowed
http://www06.eyny.com/data/cache/style_1_common.css?qbh
Allowed
http://www06.eyny.com/data/cache/css_common.css?qbh
Allowed
http://www06.eyny.com/data/cache/js_common.js?qbh
Allowed
http://www06.eyny.com/data/cache/js_show_ads.js?qbh
Allowed
http://www06.eyny.com/data/cache/common.js?qbh
Allowed
http://www06.eyny.com/static/image/common/logo.gif
Allowed
http://www06.eyny.com/data/cache/md5.js?qbh
Allowed
http://www06.eyny.com/home.php?mod=misc&ac=sendmail&rand=1667143218
Allowed
http://www06.eyny.com/data/cache/js_langconv.js?qbh
Allowed
http://www06.eyny.com/ads&channel=1&format=728x90&type=image&border=0&ajax=1
Allowed
http://www06.eyny.com/static/image/common/qmenu.png
Allowed
http://www06.eyny.com/static/image/common/search.png
Allowed
http://www06.eyny.com/static/image/common/arrwd.gif
Allowed
http://www06.eyny.com/static/image/common/px.png
Allowed
http://www06.eyny.com/static/image/common/pn.png
Allowed
http://www06.eyny.com/static/image/common/scrolltop.png
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for eyny.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of eyny.com on mobile screens.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
0

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of eyny.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of eyny.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 55
Performance 53
Accessibility 85
Best Practices 75
SEO 62
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www04.eyny.com/member.php
Updated: 30th October, 2022

0.76 seconds
First Contentful Paint (FCP)
89%
7%
4%

0.23 seconds
First Input Delay (FID)
46%
51%
3%

Simulate loading on mobile
53

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for eyny.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 2.3 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://eyny.com/
http/1.1
0
243.40099981055
236
0
302
text/html
http://www04.eyny.com/
http/1.1
243.77599987201
935.66399998963
1041
0
302
text/html
http://www04.eyny.com/member.php?mod=logging&action=login
http/1.1
935.98399986513
1453.7539999001
6453
15321
200
text/html
Document
http://www04.eyny.com/data/cache/style_1_common.css?qbh
http/1.1
1462.241999805
1594.4329998456
12903
55698
200
text/css
Stylesheet
http://www04.eyny.com/data/cache/css_common.css?qbh
http/1.1
1462.5079999678
1703.053999925
2301
7195
200
text/css
Stylesheet
http://www04.eyny.com/data/cache/js_common.js?qbh
http/1.1
1462.7279997803
1702.3599999957
2722
6728
200
text/javascript
Script
http://www04.eyny.com/data/cache/js_show_ads.js?qbh
http/1.1
1462.9829998594
1707.2059998754
663
514
200
text/javascript
Script
http://www04.eyny.com/data/cache/common.js?qbh
http/1.1
1463.0729998462
1817.5839998294
16950
55867
200
text/javascript
Script
http://www04.eyny.com/static/image/common/logo.gif
http/1.1
1826.5499998815
1950.8799999021
6739
6453
200
image/gif
Image
https://www.google.com/recaptcha/api.js?render=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW
h2
1709.5929998904
1721.3619998656
1179
884
200
text/javascript
Script
http://www04.eyny.com/data/cache/md5.js?qbh
http/1.1
1722.8659999091
1857.3719998822
1829
4730
200
text/javascript
Script
http://www04.eyny.com/home.php?mod=misc&ac=sendmail&rand=1667143238
http/1.1
1821.4239999652
1963.6559998617
942
0
200
text/html
Script
http://www04.eyny.com/data/cache/js_langconv.js?qbh
http/1.1
1826.4109999873
1944.0229998436
7551
10409
200
text/javascript
Script
http://www04.eyny.com/ads&channel=1&format=728x90&type=image&border=0&ajax=1
http/1.1
1827.8019998688
2256.3069998287
908
0
302
text/html
http://www04.eyny.com/static/image/common/qmenu.png
http/1.1
1831.5219997894
1949.0969998296
2030
1744
200
image/png
Image
http://www04.eyny.com/static/image/common/search.png
http/1.1
1832.4089997914
2074.7949997894
3220
2934
200
image/png
Image
http://www04.eyny.com/static/image/common/arrwd.gif
http/1.1
1832.9189999495
2096.4959999546
335
51
200
image/gif
Image
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
h2
1897.2819999326
1909.6339999232
162405
406468
200
text/javascript
Script
http://www04.eyny.com/static/image/common/px.png
http/1.1
1899.1729998961
2143.2049998548
494
210
200
image/png
Image
http://www04.eyny.com/static/image/common/pn.png
http/1.1
1899.8459998984
2016.6119998321
877
592
200
image/png
Image
http://www04.eyny.com/static/image/common/scrolltop.png
http/1.1
1989.3739998806
2106.3219998032
1354
1068
200
image/png
Image
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA0LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=h8o4icsd8m3
h2
2006.9069999736
2027.2669999395
24119
45640
200
text/html
Document
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/styles__ltr.css
h2
2037.3779998627
2045.1199999079
25184
52913
200
text/css
Stylesheet
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
h2
2037.760999985
2049.4909998961
162405
406468
200
text/javascript
Script
https://www.gstatic.com/recaptcha/api2/logo_48.png
h2
2123.7259998452
2126.8050000072
3101
2228
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
2124.944999814
2127.5459998287
11676
10748
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
h2
2125.7119998336
2129.9259997904
11716
10788
200
font/woff2
Font
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=NJPGLzpIZgjszqyOymHUP0XR
h2
2137.7109999303
2147.3859997932
832
102
200
text/javascript
Other
http://www04.eyny.com/member.php?mod=logging&action=login
http/1.1
2256.6129998304
2508.3779999986
6469
15225
200
text/html
XHR
https://www.google.com/recaptcha/api2/reload?k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW
h2
2408.744999906
2458.051999798
19164
32196
200
application/json
XHR
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1457.783
9.602
1830.183
65.913
1899.08
36.774
1943.635
10.219
1962.959
17.879
1985.342
23.138
2030.784
7.841
2072.358
16.992
2089.999
39.491
2138.578
15.274
2155.589
39.442
2199.275
41.937
2244.521
12.183
2259.47
33.458
2293.823
71.303
2365.404
6.921
2459.707
6.129
2465.886
23.486
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Eyny.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Eyny.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Eyny.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Eyny.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 520 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www04.eyny.com/member.php?mod=logging&action=login
518.763
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Eyny.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Avoids enormous network payloads — Total size was 486 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
162405
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
162405
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/styles__ltr.css
25184
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA0LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=h8o4icsd8m3
24119
https://www.google.com/recaptcha/api2/reload?k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW
19164
http://www04.eyny.com/data/cache/common.js?qbh
16950
http://www04.eyny.com/data/cache/style_1_common.css?qbh
12903
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
11716
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11676
http://www04.eyny.com/data/cache/js_langconv.js?qbh
7551
Uses efficient cache policy on static assets — 15 resources found
Eyny.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.gstatic.com/recaptcha/api2/logo_48.png
604800000
3101
http://www04.eyny.com/data/cache/common.js?qbh
1209600000
16950
http://www04.eyny.com/data/cache/style_1_common.css?qbh
1209600000
12903
http://www04.eyny.com/data/cache/js_langconv.js?qbh
1209600000
7551
http://www04.eyny.com/static/image/common/logo.gif
1209600000
6739
http://www04.eyny.com/static/image/common/search.png
1209600000
3220
http://www04.eyny.com/data/cache/js_common.js?qbh
1209600000
2722
http://www04.eyny.com/data/cache/css_common.css?qbh
1209600000
2301
http://www04.eyny.com/static/image/common/qmenu.png
1209600000
2030
http://www04.eyny.com/data/cache/md5.js?qbh
1209600000
1829
http://www04.eyny.com/static/image/common/scrolltop.png
1209600000
1354
http://www04.eyny.com/static/image/common/pn.png
1209600000
877
http://www04.eyny.com/data/cache/js_show_ads.js?qbh
1209600000
663
http://www04.eyny.com/static/image/common/px.png
1209600000
494
http://www04.eyny.com/static/image/common/arrwd.gif
1209600000
335
Avoids an excessive DOM size — 279 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
279
Maximum DOM Depth
18
Maximum Child Elements
13
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Eyny.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 30 requests • 486 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
30
497798
Script
9
356646
Stylesheet
3
40388
Document
2
30572
Other
6
28650
Font
2
23392
Image
8
18150
Media
0
0
Third-party
10
421781
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
7141
285
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
6857
168
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
6668
158
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA0LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=h8o4icsd8m3
4950
158
http://www04.eyny.com/member.php?mod=logging&action=login
1440
132
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
7426
94
http://www04.eyny.com/member.php?mod=logging&action=login
1572
74
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
1646
72
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
6600
68
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
7074
67
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 2.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 7.1 s
The time taken for the page to become fully interactive.
Speed Index — 5.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 520 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Reduce unused CSS — Potential savings of 34 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Eyny.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/styles__ltr.css
25184
23699
http://www04.eyny.com/data/cache/style_1_common.css?qbh
12903
11607
Preload Largest Contentful Paint image — Potential savings of 150 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://www04.eyny.com/static/image/common/search.png
150
Reduce JavaScript execution time — 1.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
1145.76
995.34
55.108
http://www04.eyny.com/member.php?mod=logging&action=login
588.26
31.244
8.172
https://www.google.com/recaptcha/api2/anchor?ar=1&k=6Ldi73wUAAAAAFjdEGzGjASm5E8Ffzwhtf2BCmMW&co=aHR0cDovL3d3dzA0LmV5bnkuY29tOjgw&hl=en&v=NJPGLzpIZgjszqyOymHUP0XR&size=invisible&cb=h8o4icsd8m3
363.772
302.536
7.704
Unattributable
124.108
6.048
0
Minimize main-thread work — 2.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1363.492
Style & Layout
478.144
Other
230.444
Script Parsing & Compilation
79.488
Rendering
64.424
Parse HTML & CSS
45.072
Garbage Collection
32.008

Metrics

Largest Contentful Paint — 6.2 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 290 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 920 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Eyny.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www04.eyny.com/data/cache/style_1_common.css?qbh
12903
480
http://www04.eyny.com/data/cache/css_common.css?qbh
2301
330
http://www04.eyny.com/data/cache/js_common.js?qbh
2722
330
http://www04.eyny.com/data/cache/js_show_ads.js?qbh
663
330
http://www04.eyny.com/data/cache/common.js?qbh
16950
630
Reduce unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.gstatic.com/recaptcha/releases/NJPGLzpIZgjszqyOymHUP0XR/recaptcha__en.js
162405
75574
Avoid multiple page redirects — Potential savings of 4,620 ms
Redirects can cause additional delays before the page can begin loading. Eyny.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://eyny.com/
630
http://www04.eyny.com/
3990
http://www04.eyny.com/member.php?mod=logging&action=login
0
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.6010000146925
https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
4.2139999568462
Reduce the impact of third-party code — Third-party code blocked the main thread for 590 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
353095
417.396
45294
172.86
23392
0
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
http://www04.eyny.com/static/image/common/logo.gif
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of eyny.com on mobile screens.
First Contentful Paint (3G) — 4530 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
85

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of eyny.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Eyny.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Navigation

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that eyny.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 19 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://eyny.com/
Allowed
http://www04.eyny.com/
Allowed
http://www04.eyny.com/member.php?mod=logging&action=login
Allowed
http://www04.eyny.com/data/cache/style_1_common.css?qbh
Allowed
http://www04.eyny.com/data/cache/css_common.css?qbh
Allowed
http://www04.eyny.com/data/cache/js_common.js?qbh
Allowed
http://www04.eyny.com/data/cache/js_show_ads.js?qbh
Allowed
http://www04.eyny.com/data/cache/common.js?qbh
Allowed
http://www04.eyny.com/static/image/common/logo.gif
Allowed
http://www04.eyny.com/data/cache/md5.js?qbh
Allowed
http://www04.eyny.com/home.php?mod=misc&ac=sendmail&rand=1667143238
Allowed
http://www04.eyny.com/data/cache/js_langconv.js?qbh
Allowed
http://www04.eyny.com/ads&channel=1&format=728x90&type=image&border=0&ajax=1
Allowed
http://www04.eyny.com/static/image/common/qmenu.png
Allowed
http://www04.eyny.com/static/image/common/search.png
Allowed
http://www04.eyny.com/static/image/common/arrwd.gif
Allowed
http://www04.eyny.com/static/image/common/px.png
Allowed
http://www04.eyny.com/static/image/common/pn.png
Allowed
http://www04.eyny.com/static/image/common/scrolltop.png
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://www04.eyny.com/static/image/common/logo.gif
199 x 128
199 x 128
398 x 256

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
62

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for eyny.com. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of eyny.com on mobile screens.
Document doesn't use legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
0

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of eyny.com. This includes details about web app manifests.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of eyny.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 169.60.163.103
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Leaseweb USA, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Whois Agent (004429433)
Organization: Whois Privacy Protection Service, Inc.
Country: US
City: Kirkland
State: WA
Post Code: 98083
Email: sctwlhds@whoisprivacyprotect.com
Phone: +1.4252740657
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 85/100
WOT Child Safety: 68/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.eyny.com
Issued By: RapidSSL Global TLS RSA4096 SHA256 2022 CA1
Valid From: 6th June, 2022
Valid To: 10th June, 2023
Subject: CN = *.eyny.com
Hash: 75281626
Issuer: CN = RapidSSL Global TLS RSA4096 SHA256 2022 CA1
O = DigiCert, Inc.
S = US
Version: 2
Serial Number: 18290389320647909869561569802233245494
Serial Number (Hex): 0DC299D138A6E4D023055E4C5E46EF36
Valid From: 6th June, 2024
Valid To: 10th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:F0:9C:85:FD:A2:9F:7D:8F:C9:68:BB:D5:D4:89:4D:1D:BE:D3:90:FF
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/RapidSSLGlobalTLSRSA4096SHA2562022CA1.crl

Full Name:
URI:http://crl4.digicert.com/RapidSSLGlobalTLSRSA4096SHA2562022CA1.crl

Certificate Policies: Policy: 2.23.140.1.2.1
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/RapidSSLGlobalTLSRSA4096SHA2562022CA1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Jun 6 15:24:39.734 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:CF:EA:DE:E2:DE:AE:50:70:4C:26:B5:
8E:1F:DE:CF:63:2D:41:89:D1:27:70:30:9D:FA:90:29:
21:2D:DF:3D:61:02:20:27:44:12:06:B4:10:A2:29:65:
DA:50:2B:2A:1B:38:F0:6C:EB:0D:0B:35:88:CB:37:C8:
4F:86:BB:1D:B4:47:7A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Jun 6 15:24:39.783 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:94:32:03:B4:B2:1D:CD:55:83:EA:64:
16:E2:A8:D1:94:AE:3B:7F:71:22:78:8E:2F:62:03:C5:
E6:90:54:D0:6E:02:20:77:97:E5:4B:69:5A:DC:D1:7C:
87:CA:F1:9F:C1:BB:C2:54:EA:3C:22:86:D9:32:13:B8:
25:34:37:DC:EA:9D:A3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Jun 6 15:24:39.778 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:68:77:BE:74:68:57:DF:0F:3F:8A:03:DE:
2D:74:EC:89:F3:51:31:C4:73:8F:96:02:CA:81:F0:87:
A0:FF:E0:5D:02:20:7D:97:7C:2B:88:3C:06:3D:76:F0:
4D:CF:CA:27:2B:4B:59:12:A3:42:50:3F:34:D4:2A:35:
3A:3B:24:B1:B2:C7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:eyny.com
DNS:*.eyny.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Date: 27th February, 2022
Server: Apache/2.0.59
X-Powered-By: PHP/5.2.17

Whois Lookup

Created: 29th August, 2003
Changed: 6th June, 2022
Expires: 29th August, 2025
Registrar: ENOM, INC.
Status: clientTransferProhibited
Nameservers: dahlia.ns.cloudflare.com
mark.ns.cloudflare.com
Owner Name: Whois Agent (004429433)
Owner Organization: Whois Privacy Protection Service, Inc.
Owner Street: PO Box 639
C/O eyny.com
Owner Post Code: 98083
Owner City: Kirkland
Owner State: WA
Owner Country: US
Owner Phone: +1.4252740657
Owner Email: sctwlhds@whoisprivacyprotect.com
Admin Name: Whois Agent
Admin Organization: Whois Privacy Protection Service, Inc.
Admin Street: PO Box 639
C/O eyny.com
Admin Post Code: 98083
Admin City: Kirkland
Admin State: WA
Admin Country: US
Admin Phone: +1.4252740657
Admin Email: sctwlhds@whoisprivacyprotect.com
Tech Name: Whois Agent
Tech Organization: Whois Privacy Protection Service, Inc.
Tech Street: PO Box 639
C/O eyny.com
Tech Post Code: 98083
Tech City: Kirkland
Tech State: WA
Tech Country: US
Tech Phone: +1.4252740657
Tech Email: sctwlhds@whoisprivacyprotect.com
Full Whois:

Domain Name: eyny.com
Registry Domain ID: 102801613_DOMAIN_COM-VRSN
Registrar WHOIS Server: WHOIS.ENOM.COM
Registrar URL: WWW.ENOM.COM
Updated Date: 2022-06-06T16:36:32.00Z
Creation Date: 2003-08-29T14:08:37.00Z
Registrar Registration Expiration Date: 2025-08-29T14:08:00.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registrant Name: Whois Agent (004429433)
Registrant Organization: Whois Privacy Protection Service, Inc.
Registrant Street: PO Box 639
Registrant Street: C/O eyny.com
Registrant City: Kirkland
Registrant State/Province: WA
Registrant Postal Code: 98083
Registrant Country: US
Registrant Phone: +1.4252740657
Registrant Phone Ext:
Registrant Fax: +1.4259744730
Registrant Email: sctwlhds@whoisprivacyprotect.com
Admin Name: Whois Agent
Admin Organization: Whois Privacy Protection Service, Inc.
Admin Street: PO Box 639
Admin Street: C/O eyny.com
Admin City: Kirkland
Admin State/Province: WA
Admin Postal Code: 98083
Admin Country: US
Admin Phone: +1.4252740657
Admin Phone Ext:
Admin Fax: +1.4259744730
Admin Email: sctwlhds@whoisprivacyprotect.com
Tech Name: Whois Agent
Tech Organization: Whois Privacy Protection Service, Inc.
Tech Street: PO Box 639
Tech Street: C/O eyny.com
Tech City: Kirkland
Tech State/Province: WA
Tech Postal Code: 98083
Tech Country: US
Tech Phone: +1.4252740657
Tech Phone Ext:
Tech Fax: +1.4259744730
Tech Email: sctwlhds@whoisprivacyprotect.com
Name Server: DAHLIA.NS.CLOUDFLARE.COM
Name Server: MARK.NS.CLOUDFLARE.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: ABUSE@ENOM.COM
Registrar Abuse Contact Phone: +1.4259744689
URL of the ICANN WHOIS Data Problem Reporting System: HTTP://WDPRS.INTERNIC.NET/
>>> Last update of WHOIS database: 2022-11-17T05:16:36.00Z <<<

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


The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do not guarantee its accuracy. By submitting a
whois query, you agree that you will use this data only for lawful
purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.

We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

Nameservers

Name IP Address
dahlia.ns.cloudflare.com 108.162.192.89
mark.ns.cloudflare.com 173.245.59.130
Related

Subdomains

Domain Subdomain
ww38
www01
www03
www08
www3

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
$3,751 USD 2/5
$12,659 USD 2/5
$568 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address