178aa.com

178aa.com is SSL secured

Free website and domain report on 178aa.com

Last Updated: 23rd June, 2022 Update Now
Overview

Snoop Summary for 178aa.com

This is a free and comprehensive report about 178aa.com. 178aa.com is hosted in Cyprus on a server with an IP address of 88.218.95.31, where EUR is the local currency and the local language is Greek. 178aa.com has the potential to be earning an estimated $2 USD per day from advertising revenue. If 178aa.com was to be sold it would possibly be worth $1,826 USD (based on the daily revenue potential of the website over a 24 month period). 178aa.com receives an estimated 873 unique visitors every day - a decent amount of traffic! This report was last updated 23rd June, 2022.

About 178aa.com

Site Preview: 178aa.com 178aa.com
Title: 178 Lottery - Professional Lottery Lottery Platform -www.178AA.com
Description: 178 Lottery - Professional Lottery Lottery Platform -www.178AA.com
Keywords and Tags: 178 lottery - professional lottery lottery platform -www.178aa.com, gambling
Related Terms: leidsa lottery, lottery computer software, lottery pro, lottery program, lottery software, lottery ticket software, lottery winning software, olg lottery, print lottery bet slips, sc lottery
Fav Icon:
Age: Over 2 years old
Domain Created: 3rd April, 2022
Domain Updated: 3rd April, 2022
Domain Expires: 3rd April, 2024
Review

Snoop Score

1/5

Valuation

$1,826 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 875,403
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 873
Monthly Visitors: 26,567
Yearly Visitors: 318,598
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $2 USD
Monthly Revenue: $76 USD
Yearly Revenue: $908 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: 178aa.com 9
Domain Name: 178aa 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 70
Performance 97
Accessibility 60
Best Practices 83
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
97

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for 178aa.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 — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.01
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 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://178aa.com/
http/1.1
0
180.40199996904
278
0
301
text/html
https://178aa.com/
h2
180.78099994455
458.01199995913
5334
24343
200
text/html
Document
https://178aa.com/web/d2/static/css/index.css
h2
469.55399995204
807.62599990703
29603
95127
200
text/css
Stylesheet
https://178aa.com/web/d2/static/css/style.css
h2
469.757999992
571.82799989823
8835
39388
200
text/css
Stylesheet
https://178aa.com/js/jquery-1.8.3.min.js
h2
470.24799999781
873.5399999423
37859
93639
200
application/javascript
Script
https://178aa.com/web/dg/static/js/mobile.js
h2
470.56799998973
803.73099993449
2471
8409
200
application/javascript
Script
https://178aa.com/js/jsmobile/jquery.touchSlider.js
h2
471.94099996705
804.39199996181
3152
10580
200
application/javascript
Script
https://178aa.com/web/d2/static/css/css2.css?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,700;0,900;1,100;1,300;1,400;1,500;1,700;1,900&display=swap
h2
472.36199991312
806.35199998505
1529
26820
200
text/css
Stylesheet
https://178aa.com/web/d2/static/cloud/icon/home_blue.png
h2
809.16899989825
1075.0779999653
4433
4112
200
image/png
Image
https://178aa.com/web/d2/static/cloud/icon/mining_line.png
h2
884.78600000963
1146.7269998975
9062
8741
200
image/png
Image
https://178aa.com/img/sef/c002/xg.png
h2
906.94399992935
1076.7119999509
61792
61542
200
image/png
Image
https://178aa.com/web/d2/static/cloud/icon/share_line.png
h2
907.17499994207
1080.9929999523
7440
7119
200
image/png
Image
https://178aa.com/web/d2/static/cloud/icon/mine_line.png
h2
907.34899998643
983.82399999537
7347
7026
200
image/png
Image
https://178aa.com/img/sef/c002/alb1.jpg
h2
920.04299990367
1276.0969999945
208969
208716
200
image/jpeg
Image
https://178aa.com/img/sef/c002/alb2.jpg
h2
920.29199993704
1091.5599999717
85540
85288
200
image/jpeg
Image
https://178aa.com/img/sef/c002/alb3.jpg
h2
921.08699993696
1298.4379999107
116005
115752
200
image/jpeg
Image
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
h2
921.53699998744
1004.5689999824
28224
27902
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/icon_17.png
h2
922.04099998344
999.8229999328
5447
5126
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/icon_18.png
h2
922.41899995133
1079.1079999181
1442
1122
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_1.png
h2
922.73799993563
1006.6089999164
14419
14097
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_2.png
h2
923.40099997818
1081.5939999884
10005
9684
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_20.png
h2
923.89499989804
1056.7789999768
10834
10512
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_5.png
h2
924.22799998894
1149.0209999029
11227
10905
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
h2
924.67799992301
929.64499990921
16756
15828
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxK.woff2
h2
925.20499997772
928.99299995042
16616
15688
200
font/woff2
Font
https://hm.baidu.com/hm.js?01f21eb7564c0a583537c99b97bb9c6a
http/1.1
984.74099999294
2067.5809999229
11914
30236
200
application/javascript
Script
https://178aa.com/img/mb/menu/kefusup.png
h2
988.41799993534
1090.8259999705
4482
4161
200
image/png
Image
https://178aa.com/web/d2/static/cloud/font/uc.ttf
h2
990.29599991627
1092.0949999709
11365
11100
200
application/octet-stream
Font
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmEU9fBBc4.woff2
h2
990.57199992239
995.78100000508
16848
15920
200
font/woff2
Font
https://178aa.com/com/baseInfo.shtml
h2
1036.3720000023
1297.6489999564
177
8
200
text/html
XHR
https://178aa.com/img/logo/thr.png
h2
1046.1149999173
1228.7459999789
10368
10046
200
image/png
Image
https://178aa.com/img/logo/qukuai.png
h2
1047.2669999581
1227.9369999887
3473
3153
200
image/png
Image
https://178aa.com/img/logo/ffc.png
h2
1047.9879999766
1229.3739999877
6082
5761
200
image/png
Image
https://178aa.com/img/logo/sedie.png
h2
1048.6379999202
1275.0919999089
3926
3606
200
image/png
Image
https://178aa.com/img/logo/pkt.png
h2
1049.4809999363
1277.1399999037
6956
6635
200
image/png
Image
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=800x600&vl=940&et=0&ja=0&ln=en-us&lo=0&rnd=637347625&si=01f21eb7564c0a583537c99b97bb9c6a&v=1.2.94&lv=1&sn=54476&r=0&ww=1350&ct=!!&u=https%3A%2F%2F178aa.com%2F&tt=178%20Lottery%20-%20Professional%20Lottery%20Lottery%20Platform%20-www.178AA.com
http/1.1
2095.2839999227
3170.7819999428
299
43
200
image/gif
Image
https://178aa.com/web/d2/static/cloud/image/shadow-grey.png
h2
4002.8879999882
4077.8379999101
454
136
200
image/png
Image
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)
503.557
17.337
924.89
17.663
942.589
6.348
948.955
64.319
1024.969
38.432
1063.482
40.218
1110.431
22.041
1140.221
11.548
2113.332
22.373
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

Eliminate render-blocking resources — Potential savings of 40 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 178aa.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)
https://178aa.com/web/d2/static/css/index.css
29603
80
https://178aa.com/js/jquery-1.8.3.min.js
37859
80
Properly size images — Potential savings of 79 KiB
Images can slow down the page's load time. 178aa.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://178aa.com/img/sef/c002/xg.png
61542
58380
https://178aa.com/web/d2/static/cloud/icon/mining_line.png
8741
8615
https://178aa.com/web/d2/static/cloud/icon/share_line.png
7119
7016
https://178aa.com/web/d2/static/cloud/icon/mine_line.png
7026
6925
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 178aa.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 178aa.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 178aa.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 28 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 178aa.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://178aa.com/web/d2/static/css/index.css
29603
28722
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 280 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)
https://178aa.com/
278.219
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. 178aa.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://178aa.com/
190
https://178aa.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 178aa.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
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://178aa.com/img/sef/c002/alb1.jpg
0
Avoids enormous network payloads — Total size was 763 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://178aa.com/img/sef/c002/alb1.jpg
208969
https://178aa.com/img/sef/c002/alb3.jpg
116005
https://178aa.com/img/sef/c002/alb2.jpg
85540
https://178aa.com/img/sef/c002/xg.png
61792
https://178aa.com/js/jquery-1.8.3.min.js
37859
https://178aa.com/web/d2/static/css/index.css
29603
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
28224
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmEU9fBBc4.woff2
16848
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
16756
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxK.woff2
16616
Avoids an excessive DOM size — 302 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
302
Maximum DOM Depth
14
Maximum Child Elements
15
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 178aa.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.1 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://178aa.com/
197.112
5.955
2.286
https://178aa.com/js/jquery-1.8.3.min.js
61.259
42.058
1.594
Unattributable
59.336
4.159
0.217
Minimizes main-thread work — 0.4 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)
Style & Layout
133.198
Other
100.153
Script Evaluation
83.779
Rendering
23.692
Parse HTML & CSS
15.663
Script Parsing & Compilation
5.164
Keep request counts low and transfer sizes small — 37 requests • 763 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
37
780963
Image
23
618226
Font
4
61585
Script
4
55396
Stylesheet
3
39967
Document
1
5334
Other
2
455
Media
0
0
Third-party
5
62433
Minimize third-party usage — Third-party code blocked the main thread for 0 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)
50220
0
12213
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
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.010002626740215
3.3064092461256E-6
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 178aa.com on mobile screens.

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.

Other

Efficiently encode images — Potential savings of 290 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://178aa.com/img/sef/c002/alb1.jpg
208716
154829
https://178aa.com/img/sef/c002/alb3.jpg
115752
84655
https://178aa.com/img/sef/c002/alb2.jpg
85288
57315
Serve images in next-gen formats — Potential savings of 433 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://178aa.com/img/sef/c002/alb1.jpg
208716
182531.45
https://178aa.com/img/sef/c002/alb3.jpg
115752
101846.55
https://178aa.com/img/sef/c002/alb2.jpg
85288
72488.35
https://178aa.com/img/sef/c002/xg.png
61542
42926.7
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
27902
23747.5
https://178aa.com/web/d2/static/cloud/image/tab_1.png
14097
10488.6
https://178aa.com/web/d2/static/cloud/image/tab_20.png
10512
9055.1

Other

Serve static assets with an efficient cache policy — 29 resources found
178aa.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://178aa.com/img/sef/c002/alb1.jpg
0
208969
https://178aa.com/img/sef/c002/alb3.jpg
0
116005
https://178aa.com/img/sef/c002/alb2.jpg
0
85540
https://178aa.com/img/sef/c002/xg.png
0
61792
https://178aa.com/web/d2/static/cloud/font/uc.ttf
0
11365
https://178aa.com/js/jquery-1.8.3.min.js
43200000
37859
https://178aa.com/web/d2/static/css/index.css
43200000
29603
https://178aa.com/web/d2/static/css/style.css
43200000
8835
https://178aa.com/js/jsmobile/jquery.touchSlider.js
43200000
3152
https://178aa.com/web/dg/static/js/mobile.js
43200000
2471
https://178aa.com/web/d2/static/css/css2.css?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,700;0,900;1,100;1,300;1,400;1,500;1,700;1,900&display=swap
43200000
1529
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
2592000000
28224
https://178aa.com/web/d2/static/cloud/image/tab_1.png
2592000000
14419
https://178aa.com/web/d2/static/cloud/image/tab_5.png
2592000000
11227
https://178aa.com/web/d2/static/cloud/image/tab_20.png
2592000000
10834
https://178aa.com/img/logo/thr.png
2592000000
10368
https://178aa.com/web/d2/static/cloud/image/tab_2.png
2592000000
10005
https://178aa.com/web/d2/static/cloud/icon/mining_line.png
2592000000
9062
https://178aa.com/web/d2/static/cloud/icon/share_line.png
2592000000
7440
https://178aa.com/web/d2/static/cloud/icon/mine_line.png
2592000000
7347
https://178aa.com/img/logo/pkt.png
2592000000
6956
https://178aa.com/img/logo/ffc.png
2592000000
6082
https://178aa.com/web/d2/static/cloud/image/icon_17.png
2592000000
5447
https://178aa.com/img/mb/menu/kefusup.png
2592000000
4482
https://178aa.com/web/d2/static/cloud/icon/home_blue.png
2592000000
4433
https://178aa.com/img/logo/sedie.png
2592000000
3926
https://178aa.com/img/logo/qukuai.png
2592000000
3473
https://178aa.com/web/d2/static/cloud/image/icon_18.png
2592000000
1442
https://178aa.com/web/d2/static/cloud/image/shadow-grey.png
2592000000
454
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://178aa.com/web/d2/static/cloud/font/uc.ttf
101.7990000546
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Registers an `unload` listener
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.
Source
60

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of 178aa.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.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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 `[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.
`<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.

Audio and video

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

Names and labels

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

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 178aa.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.
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

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Name Version
jQuery
1.8.3
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 — 1 insecure request 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://178aa.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
6
Medium
90

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 178aa.com on mobile screens.
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.

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.
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.
Links are 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 isn’t 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.
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.

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.
22

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 178aa.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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 178aa.com on 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 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) 68
Performance 75
Accessibility 60
Best Practices 83
SEO 92
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://178aa.com/
Updated: 23rd June, 2022

3.14 seconds
First Contentful Paint (FCP)
52%
22%
26%

0.02 seconds
First Input Delay (FID)
93%
4%
3%

Simulate loading on mobile
75

Performance

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

Metrics

Time to Interactive — 2.6 s
The time taken for the page to become fully interactive.
Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 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).
Cumulative Layout Shift — 0.058
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
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://178aa.com/
http/1.1
0
78.014000086114
266
0
301
text/html
https://178aa.com/
h2
78.318000072613
187.00999999419
5334
24343
200
text/html
Document
https://178aa.com/web/d2/static/css/index.css
h2
198.39800009504
363.28699998558
29603
95127
200
text/css
Stylesheet
https://178aa.com/web/d2/static/css/style.css
h2
198.64400010556
278.24700018391
8835
39388
200
text/css
Stylesheet
https://178aa.com/js/jquery-1.8.3.min.js
h2
198.82300007157
429.62600011379
37859
93639
200
application/javascript
Script
https://178aa.com/web/dg/static/js/mobile.js
h2
199.23799997196
277.54899999127
2471
8409
200
application/javascript
Script
https://178aa.com/js/jsmobile/jquery.touchSlider.js
h2
199.48900002055
301.85200017877
3152
10580
200
application/javascript
Script
https://178aa.com/web/d2/static/css/css2.css?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,700;0,900;1,100;1,300;1,400;1,500;1,700;1,900&display=swap
h2
199.87300015055
300.67500006407
1529
26820
200
text/css
Stylesheet
https://178aa.com/web/d2/static/cloud/icon/home_blue.png
h2
364.64200005867
439.25800011493
4433
4112
200
image/png
Image
https://178aa.com/web/d2/static/cloud/icon/mining_line.png
h2
437.69500008784
513.22900014929
9062
8741
200
image/png
Image
https://178aa.com/img/sef/c002/xg.png
h2
455.37100010552
755.30100008473
61792
61542
200
image/png
Image
https://178aa.com/web/d2/static/cloud/icon/share_line.png
h2
458.11000000685
534.67600001022
7440
7119
200
image/png
Image
https://178aa.com/web/d2/static/cloud/icon/mine_line.png
h2
458.29900004901
535.20600008778
7347
7026
200
image/png
Image
https://178aa.com/img/sef/c002/alb1.jpg
h2
471.45300009288
767.32700015418
208969
208716
200
image/jpeg
Image
https://178aa.com/img/sef/c002/alb2.jpg
h2
471.729000099
692.89200007915
85540
85288
200
image/jpeg
Image
https://178aa.com/img/sef/c002/alb3.jpg
h2
472.0100001432
653.39000010863
116005
115752
200
image/jpeg
Image
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
h2
472.72600000724
624.99799998477
28224
27902
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/icon_17.png
h2
473.17500016652
625.39800000377
5447
5126
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/icon_18.png
h2
474.09200016409
548.86900004931
1442
1122
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_1.png
h2
474.33600015938
585.25300002657
14419
14097
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_2.png
h2
474.64000014588
680.1460001152
10005
9684
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_20.png
h2
475.12500011362
552.5740000885
10834
10512
200
image/png
Image
https://178aa.com/web/d2/static/cloud/image/tab_5.png
h2
475.86800018325
680.78200006858
11227
10905
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
h2
476.56500013545
481.587999966
16755
15828
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxK.woff2
h2
477.04800008796
484.02200010605
16616
15688
200
font/woff2
Font
https://hm.baidu.com/hm.js?01f21eb7564c0a583537c99b97bb9c6a
http/1.1
531.88100014813
1605.1549999975
11914
30236
200
application/javascript
Script
https://178aa.com/img/mb/menu/kefusup.png
h2
533.35699997842
652.0690000616
4482
4161
200
image/png
Image
https://178aa.com/web/d2/static/cloud/font/uc.ttf
h2
534.55400001258
756.77000009455
11365
11100
200
application/octet-stream
Font
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmEU9fBBc4.woff2
h2
535.61899997294
539.92400015704
16848
15920
200
font/woff2
Font
https://178aa.com/com/baseInfo.shtml
h2
564.18600003235
758.13900004141
177
8
200
text/html
XHR
https://178aa.com/img/logo/thr.png
h2
571.78800017573
768.18500016816
10368
10046
200
image/png
Image
https://178aa.com/img/logo/qukuai.png
h2
572.98699999228
767.94599997811
3473
3153
200
image/png
Image
https://178aa.com/img/logo/ffc.png
h2
573.16699996591
758.93200002611
6082
5761
200
image/png
Image
https://178aa.com/img/logo/sedie.png
h2
573.52300011553
658.71600015089
3926
3606
200
image/png
Image
https://178aa.com/img/logo/pkt.png
h2
574.91600001231
658.00000005402
6956
6635
200
image/png
Image
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=360x640&vl=640&et=0&ja=0&ln=en-us&lo=0&rnd=9056892&si=01f21eb7564c0a583537c99b97bb9c6a&v=1.2.94&lv=1&sn=54501&r=0&ww=360&ct=!!&u=https%3A%2F%2F178aa.com%2F&tt=178%20Lottery%20-%20Professional%20Lottery%20Lottery%20Platform%20-www.178AA.com
http/1.1
1625.1250000205
2703.9489999879
299
43
200
image/gif
Image
https://178aa.com/web/d2/static/cloud/image/shadow-grey.png
h2
3546.5790000744
3621.3559999596
454
136
200
image/png
Image
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)
221.187
12.331
467.645
16.396
489.516
63.606
561.546
22.539
584.329
31.299
620.621
18.978
791.748
8.363
1640.151
14.579
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

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 178aa.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 178aa.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 178aa.com should consider minifying JS files.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 110 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)
https://178aa.com/
109.686
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. 178aa.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://178aa.com/
630
https://178aa.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 178aa.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
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://178aa.com/img/sef/c002/alb1.jpg
0
Avoids enormous network payloads — Total size was 763 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://178aa.com/img/sef/c002/alb1.jpg
208969
https://178aa.com/img/sef/c002/alb3.jpg
116005
https://178aa.com/img/sef/c002/alb2.jpg
85540
https://178aa.com/img/sef/c002/xg.png
61792
https://178aa.com/js/jquery-1.8.3.min.js
37859
https://178aa.com/web/d2/static/css/index.css
29603
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
28224
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmEU9fBBc4.woff2
16848
https://fonts.gstatic.com/s/roboto/v29/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
16755
https://fonts.gstatic.com/s/roboto/v29/KFOmCnqEu92Fr1Mu4mxK.woff2
16616
Avoids an excessive DOM size — 302 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
302
Maximum DOM Depth
14
Maximum Child Elements
15
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 178aa.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://178aa.com/
618.644
15.344
6.428
https://178aa.com/js/jquery-1.8.3.min.js
197.596
139.012
6.388
Unattributable
191.668
11.936
0.668
https://hm.baidu.com/hm.js?01f21eb7564c0a583537c99b97bb9c6a
93.9
83.136
2.06
Minimizes main-thread work — 1.1 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)
Style & Layout
424.548
Other
317.48
Script Evaluation
251.74
Rendering
72.952
Parse HTML & CSS
50.056
Script Parsing & Compilation
17.204
Keep request counts low and transfer sizes small — 37 requests • 763 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
37
780950
Image
23
618226
Font
4
61584
Script
4
55396
Stylesheet
3
39967
Document
1
5334
Other
2
443
Media
0
0
Third-party
5
62432
Minimize third-party usage — Third-party code blocked the main thread for 0 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)
12213
0.752
50219
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
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.05810546875
3.8414001464844E-5
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 — 4 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://178aa.com/
1159
127
https://178aa.com/js/jquery-1.8.3.min.js
2310
66
https://178aa.com/js/jquery-1.8.3.min.js
2376
63
https://hm.baidu.com/hm.js?01f21eb7564c0a583537c99b97bb9c6a
2040
58
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 178aa.com on mobile screens.

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.5 s
The time taken for the first image or text on the page to be rendered.

Audits

First Meaningful Paint — 2.6 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 178aa.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)
https://178aa.com/web/d2/static/css/index.css
29603
450
https://178aa.com/js/jquery-1.8.3.min.js
37859
300
Properly size images — Potential savings of 59 KiB
Images can slow down the page's load time. 178aa.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://178aa.com/img/sef/c002/xg.png
61542
39755
https://178aa.com/web/d2/static/cloud/icon/mining_line.png
8741
7874
https://178aa.com/web/d2/static/cloud/icon/share_line.png
7119
6413
https://178aa.com/web/d2/static/cloud/icon/mine_line.png
7026
6329
Reduce unused CSS — Potential savings of 28 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 178aa.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://178aa.com/web/d2/static/css/index.css
29603
28722

Metrics

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

Other

Efficiently encode images — Potential savings of 290 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://178aa.com/img/sef/c002/alb1.jpg
208716
154829
https://178aa.com/img/sef/c002/alb3.jpg
115752
84655
https://178aa.com/img/sef/c002/alb2.jpg
85288
57315
Serve images in next-gen formats — Potential savings of 433 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://178aa.com/img/sef/c002/alb1.jpg
208716
182531.45
https://178aa.com/img/sef/c002/alb3.jpg
115752
101846.55
https://178aa.com/img/sef/c002/alb2.jpg
85288
72488.35
https://178aa.com/img/sef/c002/xg.png
61542
42926.7
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
27902
23747.5
https://178aa.com/web/d2/static/cloud/image/tab_1.png
14097
10488.6
https://178aa.com/web/d2/static/cloud/image/tab_20.png
10512
9055.1
Serve static assets with an efficient cache policy — 29 resources found
178aa.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://178aa.com/img/sef/c002/alb1.jpg
0
208969
https://178aa.com/img/sef/c002/alb3.jpg
0
116005
https://178aa.com/img/sef/c002/alb2.jpg
0
85540
https://178aa.com/img/sef/c002/xg.png
0
61792
https://178aa.com/web/d2/static/cloud/font/uc.ttf
0
11365
https://178aa.com/js/jquery-1.8.3.min.js
43200000
37859
https://178aa.com/web/d2/static/css/index.css
43200000
29603
https://178aa.com/web/d2/static/css/style.css
43200000
8835
https://178aa.com/js/jsmobile/jquery.touchSlider.js
43200000
3152
https://178aa.com/web/dg/static/js/mobile.js
43200000
2471
https://178aa.com/web/d2/static/css/css2.css?family=Roboto:ital,wght@0,100;0,300;0,400;0,500;0,700;0,900;1,100;1,300;1,400;1,500;1,700;1,900&display=swap
43200000
1529
https://178aa.com/web/d2/static/cloud/image/topic_bg.png
2592000000
28224
https://178aa.com/web/d2/static/cloud/image/tab_1.png
2592000000
14419
https://178aa.com/web/d2/static/cloud/image/tab_5.png
2592000000
11227
https://178aa.com/web/d2/static/cloud/image/tab_20.png
2592000000
10834
https://178aa.com/img/logo/thr.png
2592000000
10368
https://178aa.com/web/d2/static/cloud/image/tab_2.png
2592000000
10005
https://178aa.com/web/d2/static/cloud/icon/mining_line.png
2592000000
9062
https://178aa.com/web/d2/static/cloud/icon/share_line.png
2592000000
7440
https://178aa.com/web/d2/static/cloud/icon/mine_line.png
2592000000
7347
https://178aa.com/img/logo/pkt.png
2592000000
6956
https://178aa.com/img/logo/ffc.png
2592000000
6082
https://178aa.com/web/d2/static/cloud/image/icon_17.png
2592000000
5447
https://178aa.com/img/mb/menu/kefusup.png
2592000000
4482
https://178aa.com/web/d2/static/cloud/icon/home_blue.png
2592000000
4433
https://178aa.com/img/logo/sedie.png
2592000000
3926
https://178aa.com/img/logo/qukuai.png
2592000000
3473
https://178aa.com/web/d2/static/cloud/image/icon_18.png
2592000000
1442
https://178aa.com/web/d2/static/cloud/image/shadow-grey.png
2592000000
454
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://178aa.com/web/d2/static/cloud/font/uc.ttf
222.21600008197
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Registers an `unload` listener
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.
Source
First Contentful Paint (3G) — 5190 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
60

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of 178aa.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.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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 `[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.
`<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.

Audio and video

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

Names and labels

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

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 178aa.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.
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

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Name Version
jQuery
1.8.3
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 — 1 insecure request 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://178aa.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 6 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
6
Medium
92

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 178aa.com on mobile screens.
Document uses legible font sizes — 81.98% legible text
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.
Source Selector % of Page Text Font Size
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
1.20%
8px
81.98%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
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.

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.
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.
Links are 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 isn’t 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.
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.

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.
30

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 178aa.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.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of 178aa.com on 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 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: 88.218.95.31
Continent: Europe
Country: Cyprus
Cyprus Flag
Region:
City:
Longitude: 33
Latitude: 35
Currencies: EUR
Languages: Greek
Turkish

Web Hosting Provider

Name IP Address
Enzu cloud and colocation services
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com LLC 23.220.132.43
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.178aa.com
Issued By: R3
Valid From: 4th April, 2022
Valid To: 3rd July, 2022
Subject: CN = www.178aa.com
Hash: 2869711c
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03429D5EA17B0C2A24870C51CAF85BDCC73F
Serial Number (Hex): 03429D5EA17B0C2A24870C51CAF85BDCC73F
Valid From: 4th April, 2024
Valid To: 3rd July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Apr 4 13:22:38.001 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:3A:9D:6F:5B:04:BB:17:29:6B:C3:E1:60:
C7:E2:A0:EC:8C:6E:D4:64:8E:29:B0:5D:E8:CC:D2:1B:
89:D0:BD:1A:02:20:0F:64:12:C6:C4:B8:4D:FB:C1:98:
5F:A4:87:CB:EA:0F:01:88:44:E6:35:84:28:9B:16:C7:
BD:D8:5C:15:68:84
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Apr 4 13:22:38.333 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:4C:71:85:ED:1A:ED:11:F3:B7:7B:30:47:
37:2C:3C:AC:3E:AB:8C:36:2E:DA:2B:5C:60:35:50:1A:
9D:8B:2A:6D:02:20:4B:10:C3:5D:FF:09:EA:20:57:A5:
61:58:D0:65:EF:FA:22:60:D6:28:E2:95:33:02:4B:AF:
00:5C:C8:E7:B7:B4
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:178aa.com
DNS:www.178aa.com
DNS:178.178aa.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
178aa.com. 88.218.95.31 IN 3600

NS Records

Host Nameserver Class TTL
178aa.com. ns63.domaincontrol.com. IN 3600
178aa.com. ns64.domaincontrol.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
178aa.com. ns63.domaincontrol.com. dns.jomax.net. 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200
Server: nginx
Date: 23rd June, 2022
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: *
Strict-Transport-Security: max-age=31536000

Whois Lookup

Created: 3rd April, 2022
Changed: 3rd April, 2022
Expires: 3rd April, 2024
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns63.domaincontrol.com
ns64.domaincontrol.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=178aa.com
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=178aa.com
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=178aa.com
Full Whois: Domain Name: 178aa.com
Registry Domain ID: 2686432494_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2022-04-03T03:40:18Z
Creation Date: 2022-04-03T03:40:18Z
Registrar Registration Expiration Date: 2024-04-03T03:40:18Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=178aa.com
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=178aa.com
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=178aa.com
Name Server: NS63.DOMAINCONTROL.COM
Name Server: NS64.DOMAINCONTROL.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-06-23T14:00:50Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns63.domaincontrol.com 97.74.101.42
ns64.domaincontrol.com 173.201.69.42
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address