webgarden.com

webgarden.com is SSL secured

Free website and domain report on webgarden.com

Last Updated: 15th May, 2020 Update Now
Overview

Snoop Summary for webgarden.com

This is a free and comprehensive report about webgarden.com. The domain webgarden.com is currently hosted on a server located in Prague, Hlavni mesto Praha in Czechia with the IP address 78.24.14.148, where the local currency is CZK and Czech is the local language. Webgarden.com is expected to earn an estimated $18 USD per day from advertising revenue. The sale of webgarden.com would possibly be worth $13,479 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Webgarden.com is very popular with an estimated 6,474 daily unique visitors. This report was last updated 15th May, 2020.

About webgarden.com

Site Preview: webgarden.com webgarden.com
Title:
Description:
Keywords and Tags: file system management in linux interview questions, glaustas horticulture book pdf download, internet services, kizi password reset, webgarden, www webgarden com
Related Terms:
Fav Icon:
Age: Over 26 years old
Domain Created: 8th January, 1998
Domain Updated: 30th December, 2019
Domain Expires: 7th January, 2021
Review

Snoop Score

3/5 (Great!)

Valuation

$13,479 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 73,760
Alexa Reach:
SEMrush Rank (US): 1,788,145
SEMrush Authority Score: 67
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 1,232 0
Traffic: 351 0
Cost: $34 USD $0 USD
Traffic

Visitors

Daily Visitors: 6,474
Monthly Visitors: 197,048
Yearly Visitors: 2,363,010
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $18 USD
Monthly Revenue: $562 USD
Yearly Revenue: $6,735 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 19,843,686
Referring Domains: 39,857
Referring IPs: 31,299
Webgarden.com has 19,843,686 backlinks according to SEMrush. 82% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve webgarden.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 webgarden.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://ttlink.com/
Target: https://brainspinemd.webgarden.com/

2
Source: http://tou-ka.sakura.ne.jp/rosa-gigantea/index.cgi
Target: http://paireuvshare.webgarden.com/

3
Source: http://www.marykayschildcare.com/
Target: https://panduantaruhanonline.webgarden.com/section-1/deposit-pakai-pulsa-main-judi

4
Source: https://www.roknalmadinah.com/furniture-moving-company-medina.html
Target: https://senikartu.webgarden.com/

5
Source: http://memarvakhiyal.mihanblog.com/post/141/
Target: https://zeusbola.webgarden.com/

Top Ranking Keywords (US)

1
Keyword: webgarden
Ranked Page: http://www.webgarden.com/

2
Keyword: www webgarden com
Ranked Page: http://www.webgarden.com/

3
Keyword: glaustas horticulture book pdf download
Ranked Page: https://glaustashorticulture.webgarden.com/sections/principles-of-horticulture

4
Keyword: kizi password reset
Ranked Page: https://y8games.webgarden.com/$forgotpassword

5
Keyword: file system management in linux interview questions
Ranked Page: https://narva.webgarden.com/menu/linux-interviw-questions/filesystem-management-1

Domain Analysis

Value Length
Domain: webgarden.com 13
Domain Name: webgarden 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.10 seconds
Load Time Comparison: Faster than 40% of sites

PageSpeed Insights

Avg. (All Categories) 76
Performance 85
Accessibility 87
Best Practices 77
SEO 90
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
85

Performance

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

Metrics

Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
First CPU Idle — 1.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive webgarden.com as laggy when the latency is higher than 0.05 seconds.
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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://webgarden.com/
0
339.18699994683
249
0
301
text/html
http://www.webgarden.com/
339.73400015384
651.11199999228
608
0
301
text/html
https://www.webgarden.com/
651.50999976322
1259.7659998573
5015
14507
200
text/html
Document
https://www.webgarden.com/styles.css?v=168
1271.1880002171
1642.3369999975
23676
151753
200
text/css
Stylesheet
https://www.webgarden.com/scripts.js?v=168
1271.8239999376
2361.0879997723
272570
949645
200
text/javascript
Script
https://www.google.com/jsapi
1271.9140001573
1292.9819999263
7366
26828
200
text/javascript
Script
https://www.webgarden.com/_/img/homepage/webgarden_logo_300.png
1272.1190000884
1811.1270000227
5944
5705
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-youtube.png
1272.3710001446
1817.5980001688
1931
1693
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-google-maps.png
1820.0500002131
2249.7060000896
2439
2201
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-google-analytics.png
2250.6820000708
2361.3740000874
2673
2435
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-google-ad.png
2353.9660000242
2786.3889997825
3053
2815
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-paypal.png
2363.4239998646
2473.1299998239
2656
2418
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-zopim.png
2495.120999869
2926.6849998385
2428
2190
200
image/png
Image
https://www.webgarden.com/_/img/homepage/integration/orig-smartsupp.png
2495.2790001407
2604.5610001311
2447
2209
200
image/png
Image
https://www.googleadservices.com/pagead/conversion.js
1812.2350000776
1818.9960001037
12099
28402
200
text/javascript
Script
https://c.imedia.cz/js/retargeting.js
1818.3709997684
2352.6280000806
843
877
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-PVKVSN
2496.2639999576
2519.0980001353
27919
72158
200
application/javascript
Script
https://www.webgarden.com/_/img/homepage/f350-fs8.png
2501.5799999237
2717.5309997983
36847
36607
200
image/png
Image
https://www.webgarden.com/_/img/inside/arrows2_small.png
2502.1939999424
2931.8470000289
968
731
200
image/png
Image
https://www.webgarden.com/_/common/font/RalewayDots-Regular.woff
2504.3009999208
3042.5439998507
34108
33856
200
application/font-woff
Font
https://www.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
2505.6889997795
3043.5239998624
23755
23500
200
application/octet-stream
Font
https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1060385533/?random=1589521125526&cv=9&fst=1589521125526&num=1&label=FSa0CPPApAMQ_eXQ-QM&guid=ON&resp=GooglemKTybQhCsO&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_his=2&u_tz=-420&u_java=false&u_nplug=0&u_nmime=0&sendb=1&ig=1&frm=0&url=https%3A%2F%2Fwww.webgarden.com%2F&tiba=Create%20a%20website%20for%20free%20%7C%20Webgarden&hn=www.googleadservices.com&rfmt=3&fmt=4
2535.5329997838
2544.0639997832
2610
1617
200
text/javascript
Script
https://toplist.cz/dot.asp?id=184372&random=17426209
2539.9009999819
3083.6350000463
593
42
200
image/gif
Image
https://toplist.cz/dot.asp?id=882907&random=35608339
2540.1479997672
2882.3139998131
593
42
200
image/gif
Image
https://www.google-analytics.com/analytics.js
2540.721999947
2545.2680001035
19103
45892
200
text/javascript
Script
https://c.imedia.cz/retargeting?id=16758&category=&itemId=&url=https%3A%2F%2Fwww.webgarden.com%2F
2541.8679998256
2671.8540000729
562
43
200
image/gif
Image
https://www.webgarden.com/_/common/img/lightview/prev.png
2572.3640001379
2682.0109998807
656
419
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/topclose.png
2572.742999997
3016.0869997926
668
431
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/close_large.png
2573.0619998649
3018.3759997599
881
644
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/close_small.png
2573.1830000877
2682.415000163
596
359
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/loading.gif
2573.4129999764
2791.2800000049
2033
1795
200
image/gif
Image
https://www.webgarden.com/_/common/img/lightview/inner_slideshow_stop.png
2573.6810001545
3013.2309999317
606
369
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/inner_prev.png
2573.8909998909
2682.7630000189
463
227
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/inner_next.png
2573.9930002019
3007.5249997899
465
229
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/controller_prev.png
2574.1300000809
3009.0089999139
731
494
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/controller_slideshow_stop.png
2574.2139997892
3007.0710000582
750
513
200
image/png
Image
https://www.google.com/pagead/1p-user-list/1060385533/?random=1589521125526&cv=9&fst=1589518800000&num=1&label=FSa0CPPApAMQ_eXQ-QM&guid=ON&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_his=2&u_tz=-420&u_java=false&u_nplug=0&u_nmime=0&sendb=1&frm=0&url=https%3A%2F%2Fwww.webgarden.com%2F&tiba=Create%20a%20website%20for%20free%20%7C%20Webgarden&fmt=3&is_vtc=1&random=2763028697&resp=GooglemKTybQhCsO&rmt_tld=0&ipr=y
2586.823000107
2599.2339998484
781
42
200
image/gif
Image
https://www.google-analytics.com/plugins/ua/ecommerce.js
2602.3630001582
2606.2460001558
1373
1403
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=436842146&t=pageview&_s=1&dl=https%3A%2F%2Fwww.webgarden.com%2F&ul=en-us&de=UTF-8&dt=Create%20a%20website%20for%20free%20%7C%20Webgarden&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAAT~&jid=2087637538&gjid=530891251&cid=878289712.1589521126&tid=UA-2760339-6&_gid=2138036408.1589521126&_r=1&z=1222137632
2640.1669997722
2644.6290002204
630
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j82&a=436842146&t=pageview&_s=1&dl=https%3A%2F%2Fwww.webgarden.com%2F&dp=%2FHP&ul=en-us&de=UTF-8&dt=Create%20a%20website%20for%20free%20%7C%20Webgarden&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YGDAgAAT~&jid=1638430468&gjid=1663174202&cid=878289712.1589521126&tid=UA-2760339-8&_gid=2138036408.1589521126&gtm=2wg561PVKVSN&cd3=Ostatn%C3%AD&z=1579034709
2640.285000205
2643.1510001421
643
35
200
image/gif
Image
https://stats.g.doubleclick.net/r/collect?t=dc&aip=1&_r=3&v=1&_v=j82&tid=UA-2760339-8&cid=878289712.1589521126&jid=1638430468&gjid=1663174202&_gid=2138036408.1589521126&_u=YGDAgAAT~&z=1335947930
2640.6459999271
2644.1739997827
703
35
200
image/gif
Image
https://www.webgarden.com/_/common/img/lightview/controller_next.png
3016.7060000822
3125.3680000082
728
491
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/controller_slideshow_play.png
3016.8150002137
3126.2829997577
777
540
200
image/png
Image
https://www.webgarden.com/_/common/img/lightview/controller_close.png
3017.1500002034
3125.889999792
773
536
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)
1289.247
6.772
1670.981
6.806
2430.033
97.038
2527.803
22.347
2550.428
19.381
2571.216
6.385
2578.008
27.747
2614.286
9.751
2624.497
43.566
2668.132
6.909
3037.026
12.629
3069.993
6.496
3077.412
8.212
3090.742
8.905
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Webgarden.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Webgarden.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Webgarden.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Webgarden.com should consider minifying JS files.
Remove unused CSS — Potential savings of 22 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Webgarden.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
https://www.webgarden.com/styles.css?v=168
23676
22814
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 25 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
https://www.webgarden.com/_/img/homepage/f350-fs8.png
36607
25923
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Webgarden.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.

Diagnostics

Avoids enormous network payloads — Total size was 495 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://www.webgarden.com/scripts.js?v=168
272570
https://www.webgarden.com/_/img/homepage/f350-fs8.png
36847
https://www.webgarden.com/_/common/font/RalewayDots-Regular.woff
34108
https://www.googletagmanager.com/gtm.js?id=GTM-PVKVSN
27919
https://www.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
23755
https://www.webgarden.com/styles.css?v=168
23676
https://www.google-analytics.com/analytics.js
19103
https://www.googleadservices.com/pagead/conversion.js
12099
https://www.google.com/jsapi
7366
https://www.webgarden.com/_/img/homepage/webgarden_logo_300.png
5944
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
14
Maximum Child Elements
14
Avoid chaining critical requests — 7 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Webgarden.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)
Other
157.198
18.928
0.952
https://www.webgarden.com/scripts.js?v=168
109.535
87.982
17.45
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)
Script Evaluation
184.198
Other
67.377
Style & Layout
44.025
Script Parsing & Compilation
32.841
Rendering
17.202
Parse HTML & CSS
13.203
Keep request counts low and transfer sizes small — 44 requests • 495 KB
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
44
507312
Script
8
343883
Image
30
76018
Font
2
57863
Stylesheet
1
23676
Document
1
5015
Other
2
857
Media
0
0
Third-party
14
75818
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 Size (Bytes) Main-Thread Blocking Time (Ms)
27919
0
21749
0
15412
0
8147
0
1405
0

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.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.
Speed Index — 2.1 s
The time taken for the page contents to be visibly populated.

Opportunities

Eliminate render-blocking resources — Potential savings of 470 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Webgarden.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://www.webgarden.com/styles.css?v=168
23676
110
https://www.webgarden.com/scripts.js?v=168
272570
310
https://www.google.com/jsapi
7366
230
Avoid multiple page redirects — Potential savings of 380 ms
Redirects can cause additional delays before the page can begin loading. Webgarden.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://webgarden.com/
0
http://www.webgarden.com/
190
https://www.webgarden.com/
190

Opportunities

Reduce server response times (TTFB) — Root document took 610 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Serve static assets with an efficient cache policy — 29 resources found
Webgarden.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) Size (Bytes)
https://www.webgarden.com/_/img/homepage/f350-fs8.png
0
36847
https://www.webgarden.com/_/common/font/RalewayDots-Regular.woff
0
34108
https://www.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
0
23755
https://www.webgarden.com/_/img/homepage/webgarden_logo_300.png
0
5944
https://www.webgarden.com/_/img/homepage/integration/orig-google-ad.png
0
3053
https://www.webgarden.com/_/img/homepage/integration/orig-google-analytics.png
0
2673
https://www.webgarden.com/_/img/homepage/integration/orig-paypal.png
0
2656
https://www.webgarden.com/_/img/homepage/integration/orig-smartsupp.png
0
2447
https://www.webgarden.com/_/img/homepage/integration/orig-google-maps.png
0
2439
https://www.webgarden.com/_/img/homepage/integration/orig-zopim.png
0
2428
https://www.webgarden.com/_/common/img/lightview/loading.gif
0
2033
https://www.webgarden.com/_/img/homepage/integration/orig-youtube.png
0
1931
https://www.webgarden.com/_/img/inside/arrows2_small.png
0
968
https://www.webgarden.com/_/common/img/lightview/close_large.png
0
881
https://www.webgarden.com/_/common/img/lightview/controller_slideshow_play.png
0
777
https://www.webgarden.com/_/common/img/lightview/controller_close.png
0
773
https://www.webgarden.com/_/common/img/lightview/controller_slideshow_stop.png
0
750
https://www.webgarden.com/_/common/img/lightview/controller_prev.png
0
731
https://www.webgarden.com/_/common/img/lightview/controller_next.png
0
728
https://www.webgarden.com/_/common/img/lightview/topclose.png
0
668
https://www.webgarden.com/_/common/img/lightview/prev.png
0
656
https://www.webgarden.com/_/common/img/lightview/inner_slideshow_stop.png
0
606
https://www.webgarden.com/_/common/img/lightview/close_small.png
0
596
https://www.webgarden.com/_/common/img/lightview/inner_next.png
0
465
https://www.webgarden.com/_/common/img/lightview/inner_prev.png
0
463
https://www.google-analytics.com/plugins/ua/ecommerce.js
3600000
1373
https://www.google-analytics.com/analytics.js
7200000
19103
https://www.webgarden.com/scripts.js?v=168
1209600000
272570
https://www.webgarden.com/styles.css?v=168
1209600000
23676
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://www.webgarden.com/_/common/font/RalewayDots-Regular.woff
538.24299992993
https://www.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
537.83500008285
87

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of webgarden.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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Webgarden.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Webgarden.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Webgarden.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
`<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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 `[alt]` 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.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

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.

Contrast

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

Navigation

Some elements have 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.
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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
77

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Prototype
1.7.1
Scriptaculous
1.9.0
SWFObject
2.3
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 2 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
http://webgarden.com/
http://www.webgarden.com/
Uses `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.
URL Location
https://www.googleadservices.com/pagead/conversion.js
line: 56
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for webgarden.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.
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.

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 webgarden.com on mobile screens.

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

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides 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.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 2 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
http://webgarden.com/
http://www.webgarden.com/
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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 webgarden.com on mobile screens.

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) 76
Performance 57
Accessibility 81
Best Practices 92
SEO 98
Progressive Web App 52
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
57

Performance

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

Metrics

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

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive webgarden.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 30 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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://webgarden.com/
0
214.76799994707
249
0
301
text/html
http://www.webgarden.com/
215.18499986269
437.33499990776
607
0
301
text/html
https://www.webgarden.com/
437.71900003776
619.51099988073
612
0
301
text/html
http://m.webgarden.com/
619.84100006521
964.77099996991
607
0
301
text/html
https://m.webgarden.com/
965.12100007385
1841.6649999563
4601
31166
200
text/html
Document
https://m.webgarden.com/styles.css?v=168
1854.4870000333
2450.9699998889
16517
106680
200
text/css
Stylesheet
https://m.webgarden.com/scripts.js?v=168
1854.6229999047
2584.2259998899
51790
177897
200
text/javascript
Script
https://www.google.com/jsapi
1854.9369999673
1859.1549999546
550
0
302
text/html
https://m.webgarden.com/_/img/homepage/webgarden_logo.png
1855.1749999169
2285.5640000198
6391
6152
200
image/png
Image
https://m.webgarden.com/_/img/inside/webgarden_logo.png
1855.3710000124
1963.7629999779
2849
2611
200
image/png
Image
https://www.gstatic.com/charts/loader.js
1859.3299998902
1869.917999953
14458
44912
200
text/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-PVKVSN
2618.3159998618
2648.4499999788
27919
72158
200
application/javascript
Script
https://m.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
2625.0879999716
2828.1089998782
23755
23500
200
application/octet-stream
Font
http://toplist.cz/dot.asp?id=184372&random=52857995
2660.1909999736
2875.6389999762
176
0
301
http://toplist.cz/dot.asp?id=1484802&random=97796920
2660.6840000022
2874.3610000238
177
0
301
https://www.google-analytics.com/analytics.js
2682.5439999811
2686.9759999681
19103
45892
200
text/javascript
Script
https://www.google-analytics.com/plugins/ua/ecommerce.js
2696.3049999904
2699.8000000603
1374
1403
200
text/javascript
Script
https://toplist.cz/dot.asp?id=1484802&random=97796920
2874.6090000495
3217.6289998461
593
42
200
image/gif
Image
https://toplist.cz/dot.asp?id=184372&random=52857995
2875.7690000348
3209.1200000141
593
42
200
image/gif
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)
1863.506
6.654
2612.337
28.619
2641.044
34.887
2676.08
5.683
2692.464
10.308
2709.86
23.045
2851.479
12.425
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Webgarden.com should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 3 KB
Time to Interactive can be slowed down by resources on the page. Webgarden.com should consider lazy-loading offscreen and hidden images.
URL Size (Bytes) Potential Savings (Bytes)
https://m.webgarden.com/_/img/inside/webgarden_logo.png
2611
2611
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Webgarden.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Webgarden.com should consider minifying JS files.
Remove unused CSS — Potential savings of 16 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Webgarden.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
https://m.webgarden.com/styles.css?v=168
16517
16213
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Webgarden.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.

Diagnostics

Avoids enormous network payloads — Total size was 169 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://m.webgarden.com/scripts.js?v=168
51790
https://www.googletagmanager.com/gtm.js?id=GTM-PVKVSN
27919
https://m.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
23755
https://www.google-analytics.com/analytics.js
19103
https://m.webgarden.com/styles.css?v=168
16517
https://www.gstatic.com/charts/loader.js
14458
https://m.webgarden.com/_/img/homepage/webgarden_logo.png
6391
https://m.webgarden.com/
4601
https://m.webgarden.com/_/img/inside/webgarden_logo.png
2849
https://www.google-analytics.com/plugins/ua/ecommerce.js
1374
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Webgarden.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.2 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)
Other
372.012
11.136
3.172
https://www.google-analytics.com/analytics.js
91.184
85.564
5.62
https://m.webgarden.com/scripts.js?v=168
86.492
60.076
16.06
https://www.googletagmanager.com/gtm.js?id=GTM-PVKVSN
59.864
53.136
6.728
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
238.076
Style & Layout
173.9
Other
118.456
Script Parsing & Compilation
41.192
Parse HTML & CSS
39.264
Rendering
37
Keep request counts low and transfer sizes small — 19 requests • 169 KB
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
19
172921
Script
5
114644
Font
1
23755
Stylesheet
1
16517
Image
4
10426
Document
1
4601
Other
7
2978
Media
0
0
Third-party
9
64943
Minimize third-party usage — Third-party code blocked the main thread for 30 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 Size (Bytes) Main-Thread Blocking Time (Ms)
20477
33.392
27919
0
14458
0
550
0

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.

Metrics

Time to Interactive — 5.0 s
The time taken for the page to become fully interactive.
First CPU Idle — 5.0 s
The time taken for the page's main thread to be quiet enough to handle input.

Diagnostics

Serve static assets with an efficient cache policy — 8 resources found
Webgarden.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) Size (Bytes)
https://m.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
0
23755
https://m.webgarden.com/_/img/homepage/webgarden_logo.png
0
6391
https://m.webgarden.com/_/img/inside/webgarden_logo.png
0
2849
https://www.gstatic.com/charts/loader.js
3600000
14458
https://www.google-analytics.com/plugins/ua/ecommerce.js
3600000
1374
https://www.google-analytics.com/analytics.js
7200000
19103
https://m.webgarden.com/scripts.js?v=168
1209600000
51790
https://m.webgarden.com/styles.css?v=168
1209600000
16517
Avoid an excessive DOM size — 860 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
860
Maximum DOM Depth
40
Maximum Child Elements
10

Metrics

First Contentful Paint — 4.5 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 4.5 s
The time taken for the primary content of the page to be rendered.
Speed Index — 6.4 s
The time taken for the page contents to be visibly populated.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,620 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Webgarden.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://m.webgarden.com/styles.css?v=168
16517
330
https://m.webgarden.com/scripts.js?v=168
51790
930
https://www.google.com/jsapi
550
780
Reduce server response times (TTFB) — Root document took 880 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 2,370 ms
Redirects can cause additional delays before the page can begin loading. Webgarden.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://webgarden.com/
0
http://www.webgarden.com/
630
https://www.webgarden.com/
630
http://m.webgarden.com/
480
https://m.webgarden.com/
630

Diagnostics

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://m.webgarden.com/_/common/font/OpenSans-CondensedLight.woff2
203.02099990658

Other

First Contentful Paint (3G) — 8967 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
81

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of webgarden.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.
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.
`[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-*]` 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.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Webgarden.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Webgarden.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Webgarden.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
`<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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 `[alt]` 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>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

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

`[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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
92

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Prototype
1.7.1
Scriptaculous
1.9.0
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 5 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
http://webgarden.com/
http://www.webgarden.com/
http://m.webgarden.com/
http://toplist.cz/dot.asp?id=184372&random=52857995
http://toplist.cz/dot.asp?id=1484802&random=97796920
98

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for webgarden.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 webgarden.com on mobile screens.
Document uses legible font sizes — 100% 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
Legible text
100.00%
≥ 12px

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

Mobile Friendly

Tap targets are not sized appropriately — 84% 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.
Tap Target Size Overlapping Target
86x15
163x17

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

Progressive Web App

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

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 webgarden.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides 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.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 5 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
http://webgarden.com/
http://www.webgarden.com/
http://m.webgarden.com/
http://toplist.cz/dot.asp?id=184372&random=52857995
http://toplist.cz/dot.asp?id=1484802&random=97796920
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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

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: 78.24.14.148
Continent: Europe
Country: Czechia
Czechia Flag
Region: Hlavni mesto Praha
City: Prague
Longitude: 14.4001
Latitude: 50.1019
Currencies: CZK
Languages: Czech
Slovak

Web Hosting Provider

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
GRANSY S.R.O D/B/A SUBREG.CZ 185.82.212.52
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: webgarden.com
Issued By: Let's Encrypt Authority X3
Valid From: 11th April, 2020
Valid To: 10th July, 2020
Subject: CN = webgarden.com
Hash: 51fc1031
Issuer: CN = Let's Encrypt Authority X3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03417FC2906F9F807833DB8CAF68F242B034
Serial Number (Hex): 03417FC2906F9F807833DB8CAF68F242B034
Valid From: 11th April, 2024
Valid To: 10th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
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://ocsp.int-x3.letsencrypt.org
CA Issuers - URI:http://cert.int-x3.letsencrypt.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
Timestamp : Apr 12 00:20:21.366 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:41:58:B3:B8:7B:92:8C:FA:86:56:7C:C2:
BC:55:65:BF:20:DA:0C:0F:A6:DD:18:04:5A:DD:7E:4D:
E6:92:41:0B:02:20:66:B9:AE:4A:B8:56:91:C9:E4:67:
EA:22:FA:24:DD:8E:D5:C4:F7:37:FE:EB:B4:8A:AC:42:
FC:64:8D:82:6B:E5
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
Timestamp : Apr 12 00:20:21.344 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:11:5C:6B:81:FC:22:1A:C0:89:98:E5:25:
2B:09:F5:EA:34:B3:85:21:2D:0B:0D:37:66:D8:78:09:
AE:12:CD:02:02:21:00:FC:57:5A:10:2C:47:FE:34:47:
80:25:88:93:86:F6:79:FD:59:C2:6B:A5:02:1D:56:4A:
BA:60:D7:26:DC:03:D7
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:webgarden.com
DNS:*.webgarden.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 403 Forbidden
Server: nginx/1.6.2
Date: 15th May, 2020
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: 14th May, 2020
Connection: keep-alive
Pragma: no-cache
Set-Cookie: *

Whois Lookup

Created: 8th January, 1998
Changed: 30th December, 2019
Expires: 7th January, 2021
Registrar: GRANSY S.R.O D/B/A SUBREG.CZ
Status: ok
Nameservers: ns.gransy.com
ns2.gransy.com
ns3.gransy.com
Owner Name: Not Disclosed Not Disclosed
Owner Organization: R2B2 s.r.o.
Owner Street: Not Disclosed
Owner Post Code: Not Disclosed
Owner City: Not Disclosed
Owner Country: CZ
Owner Phone: Not Disclosed
Owner Email: webproxy@whoisprotection.domains
Admin Name: Not Disclosed Not Disclosed
Admin Street: Not Disclosed
Admin Post Code: Not Disclosed
Admin City: Not Disclosed
Admin State: Not Disclosed
Admin Country: Not Disclosed
Admin Phone: Not Disclosed
Admin Email: webproxy@whoisprotection.domains
Tech Name: Not Disclosed Not Disclosed
Tech Street: Not Disclosed
Tech Post Code: Not Disclosed
Tech City: Not Disclosed
Tech State: Not Disclosed
Tech Country: Not Disclosed
Tech Phone: Not Disclosed
Tech Email: webproxy@whoisprotection.domains
Full Whois:
Domain Name: webgarden.com
Registry Domain ID: 5139171_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.regtons.com
Registrar URL: http://regtons.com
Updated Date: 2019-12-30T00:00:00Z
Creation Date: 1998-01-08T00:00:00Z
Registrar Registration Expiration Date: 2021-01-07T00:00:00Z
Registrar: GRANSY S.R.O D/B/A SUBREG.CZ
Registrar IANA ID: 1505
Registrar Abuse Contact Email: abuse@regtons.com
Registrar Abuse Contact Phone: +420.734463373
Reseller: R2B2 s.r.o.
Domain Status: ok https://www.icann.org/epp#ok
Registry Registrant ID: Not Disclosed
Registrant Name: Not Disclosed Not Disclosed
Registrant Organization: R2B2 s.r.o.
Registrant Street: Not Disclosed
Registrant City: Not Disclosed
Registrant State/Province:
Registrant Postal Code: Not Disclosed
Registrant Country: CZ
Registrant Phone: Not Disclosed
Registrant Phone Ext: Not Disclosed
Registrant Fax: Not Disclosed
Registrant Fax Ext: Not Disclosed
Registrant Email: webproxy@whoisprotection.domains
Registry Admin ID: Not Disclosed
Admin Name: Not Disclosed Not Disclosed
Admin Organization:
Admin Street: Not Disclosed
Admin City: Not Disclosed
Admin State/Province: Not Disclosed
Admin Postal Code: Not Disclosed
Admin Country: Not Disclosed
Admin Phone: Not Disclosed
Admin Phone Ext: Not Disclosed
Admin Fax: Not Disclosed
Admin Fax Ext: Not Disclosed
Admin Email: webproxy@whoisprotection.domains
Registry Tech ID: Not Disclosed
Tech Name: Not Disclosed Not Disclosed
Tech Organization:
Tech Street: Not Disclosed
Tech City: Not Disclosed
Tech State/Province: Not Disclosed
Tech Postal Code: Not Disclosed
Tech Country: Not Disclosed
Tech Phone: Not Disclosed
Tech Phone Ext: Not Disclosed
Tech Fax: Not Disclosed
Tech Fax Ext: Not Disclosed
Tech Email: webproxy@whoisprotection.domains
Name Server: ns.gransy.com
Name Server: ns2.gransy.com
Name Server: ns3.gransy.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-05-15T00:00:00Z <<<

Nameservers

Name IP Address
ns.gransy.com 95.179.136.180
ns2.gransy.com 217.69.4.49
ns3.gransy.com 77.78.126.35
Related

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$461 USD
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$1,052 USD 2/5
$3,500 USD 3/5
$967 USD 2/5
$1,011 USD 2/5
$3,107 USD 2/5