candy.com

candy.com is SSL secured

Free website and domain report on candy.com

Last Updated: 31st July, 2021 Update Now
Overview

Snoop Summary for candy.com

This is a free and comprehensive report about candy.com. Candy.com is hosted in United States on a server with an IP address of 104.21.20.180, where the local currency is USD and English is the local language. Candy.com has the potential to be earning an estimated $6 USD per day from advertising revenue. If candy.com was to be sold it would possibly be worth $4,423 USD (based on the daily revenue potential of the website over a 24 month period). Candy.com is quite popular with an estimated 2,121 daily unique visitors. This report was last updated 31st July, 2021.

About candy.com

Site Preview: candy.com candy.com
Title: CANDY: A Digital Collectible Experience
Description: Crave. Collect. Connect. Being a true fan is no longer just a spectator sport.
Keywords and Tags: online shopping
Related Terms: candy, candy fundraisers, collect, collect it.de, icelandic candy, longer
Fav Icon:
Age: Over 29 years old
Domain Created: 17th August, 1994
Domain Updated: 28th May, 2021
Domain Expires: 2nd October, 2028
Review

Snoop Score

3/5 (Great!)

Valuation

$4,423 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 266,984
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: 2,121
Monthly Visitors: 64,560
Yearly Visitors: 774,208
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $184 USD
Yearly Revenue: $2,206 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: candy.com 9
Domain Name: candy 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.65 seconds
Load Time Comparison: Faster than 54% of sites

PageSpeed Insights

Avg. (All Categories) 84
Performance 77
Accessibility 90
Best Practices 80
SEO 91
Progressive Web App 82
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://candy.com/
Updated: 31st July, 2021

1.46 seconds
First Contentful Paint (FCP)
84%
12%
4%

0.00 seconds
First Input Delay (FID)
97%
1%
2%

Simulate loading on desktop
77

Performance

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

Metrics

Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.3 s
The time taken for the page to become fully interactive.
Total Blocking Time — 70 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).

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Candy.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Candy.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Candy.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Candy.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Candy.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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 80 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://candy.com/
80.668
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Candy.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://candy.com/
190
https://candy.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Candy.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 — Potential savings of 12 KiB
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.
URL Potential Savings (Bytes)
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
11781
https://candy.com/static/js/2.d26960df.chunk.js
127
https://connect.facebook.net/en_US/fbevents.js
44
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://candy.com/static/media/statics_SF_H4k.158e0b98.png
0

Diagnostics

Avoids enormous network payloads — Total size was 1,423 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://candy.com/static/media/statics_SF_H4k.158e0b98.png
285120
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
273613
https://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
233627
https://candy.com/static/js/2.d26960df.chunk.js
147177
https://candy.com/static/media/statics_SF_H1080.68e5c671.png
88988
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
88823
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
74482
https://candy.com/static/js/main.09495500.chunk.js
64853
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
62948
https://www.googletagmanager.com/gtag/js?id=AW-365421231&l=dataLayer&cx=c
39509
Avoids an excessive DOM size — 50 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
50
Maximum DOM Depth
10
Maximum Child Elements
10
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Candy.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://candy.com/static/js/main.09495500.chunk.js
159.8
157.523
2.277
https://candy.com/
110.992
4.449
2.344
Unattributable
94.893
0.414
0
https://candy.com/static/js/2.d26960df.chunk.js
73.508
54.852
9.92
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
61.017
53.535
4.857
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
351.56
Other
127.34
Rendering
58.529
Script Parsing & Compilation
33.235
Style & Layout
27.876
Parse HTML & CSS
7.542
Keep request counts low and transfer sizes small — 33 requests • 15,946 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
33
16328278
Media
4
14871279
Font
2
507240
Image
9
504942
Script
11
438172
Document
2
4043
Stylesheet
1
1432
Other
4
1170
Third-party
18
230548
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)
102684
0
102457
0
17636
0
5930
0
763
0
383
0
0
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.14571863359095
0.14292232718941
div
0.026441037884967
div
0.025056031138612
div
0.023434758535525
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://candy.com/static/js/2.d26960df.chunk.js
1220
182
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

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://candy.com/
http/1.1
0
54.315000306815
787
0
301
https://candy.com/
h2
55.046000052243
134.71599994227
3059
4710
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
h2
153.70200015604
180.48800015822
62948
166593
200
application/javascript
Script
https://platform.twitter.com/oct.js
http/1.1
154.1740000248
211.19000017643
383
0
301
https://candy.com/static/css/main.475b7c0f.chunk.css
h2
154.47100019082
210.94000013545
1432
872
200
text/css
Stylesheet
https://candy.com/static/js/2.d26960df.chunk.js
h2
154.76100007072
285.75700009242
147177
526563
200
application/javascript
Script
https://candy.com/static/js/main.09495500.chunk.js
h2
155.06400028244
238.07700024918
64853
103539
200
application/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
h2
246.83600012213
263.87999998406
26621
100785
200
application/x-javascript
Script
https://static.ads-twitter.com/oct.js
h2
211.57400030643
226.59699991345
2480
5160
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-8C9XEDS6Q6&gtm=2oe7s0&_p=258255835&sr=800x600&ul=en-us&cid=602551808.1627694241&_s=1&dl=https%3A%2F%2Fcandy.com%2F&dt=CANDY%3A%20A%20Digital%20Collectible%20Experience&sid=1627694240&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1
238.38700028136
242.76600033045
0
0
-1
Ping
https://www.googletagmanager.com/gtag/js?id=AW-365421231&l=dataLayer&cx=c
h2
247.23300011829
266.33800007403
39509
97610
200
application/javascript
Script
https://static.ads-twitter.com/uwt.js
h2
247.54599994048
262.4270003289
2480
5160
200
application/javascript
Script
https://t.co/i/adsct?type=javascript&version=2.0.1&p_id=Twitter&p_user_id=0&txn_id=o646q&events=%5B%5B%22pageview%22%2Cnull%5D%5D&tw_sale_amount=0&tw_order_quantity=0&tw_iframe_status=0&tw_document_href=https%3A%2F%2Fcandy.com%2F
h2
270.62300033867
315.20600011572
695
43
200
image/gif
Image
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
h2
292.52299992368
314.32799994946
74482
258708
200
application/x-javascript
Script
https://www.googleadservices.com/pagead/conversion_async.js
h2
311.3959999755
318.66000033915
14688
36573
200
text/javascript
Script
https://candy.com/static/media/statics_LAD_1080.8486f87b.png
h2
491.81800009683
576.72600029036
38972
37939
200
image/png
Image
data
491.74900026992
491.90300004557
0
2952
200
image/png
Image
data
492.25400015712
492.40500014275
0
3629
200
image/png
Image
data
492.71700019017
492.83199990168
0
4847
200
image/png
Image
data
493.10800014064
493.20500018075
0
4400
200
image/png
Image
data
494.97999995947
495.16700021923
0
9958
200
image/png
Image
data
495.55200012401
495.73100032285
0
5087
200
image/png
Image
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
h2
496.86999991536
597.27100003511
88823
87786
200
image/png
Image
https://candy.com/static/media/statics_SF_H1080.68e5c671.png
h2
497.09099996835
601.16400010884
88988
87956
200
image/png
Image
data
497.25200003013
497.40000022575
0
5311
200
image/png
Image
https://candy.com/static/media/statics_SF_H4k.158e0b98.png
h2
498.32900008187
627.41900002584
285120
284079
200
image/png
Image
https://analytics.twitter.com/i/adsct?type=javascript&version=2.0.1&p_id=Twitter&p_user_id=0&txn_id=o646q&events=%5B%5B%22pageview%22%2Cnull%5D%5D&tw_sale_amount=0&tw_order_quantity=0&tw_iframe_status=0&tpx_cb=twttr.conversion.loadPixels&tw_document_href=https%3A%2F%2Fcandy.com%2F
h2
499.8790002428
533.67200028151
970
31
200
application/javascript
Script
https://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
h2
503.36500024423
605.09900003672
233627
232576
200
binary/octet-stream
Font
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
h2
503.99600015953
581.36900002137
273613
272560
200
binary/octet-stream
Font
https://googleads.g.doubleclick.net/pagead/viewthroughconversion/365421231/?random=1627694241086&cv=9&fst=1627694241086&num=1&bg=ffffff&guid=ON&resp=GooglemKTybQhCsO&eid=376635471&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&gtm=2oa7s0&sendb=1&ig=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fcandy.com%2F&tiba=CANDY%3A%20A%20Digital%20Collectible%20Experience&hn=www.googleadservices.com&async=1&rfmt=3&fmt=4
h2
559.92500018328
567.88700027391
1964
1652
200
text/javascript
Script
https://www.facebook.com/tr/?id=320087963089791&ev=PageView&dl=https%3A%2F%2Fcandy.com%2F%23%2F&rl=&if=false&ts=1627694241114&sw=800&sh=600&v=2.9.44&r=stable&ec=0&o=30&fbp=fb.1.1627694241112.26873357&it=1627694240820&coo=false&rqm=GET
h2
585.48500016332
599.52000016347
625
44
200
image/gif
Image
https://candy.com/static/media/BlackC-1080.66f04aba.mp4
h2
603.41199999675
777.19599986449
3720804
3145728
206
video/mp4
Media
https://candy.com/static/media/SF_CandyBlink.242cf303.mp4
h2
605.9620003216
817.78800021857
4328246
3145728
206
video/mp4
Media
https://candy.com/static/media/LadRing564x638.410e70b4.mp4
h2
608.71700011194
866.10099999234
6822229
3145728
206
video/mp4
Media
https://candy.com/static/media/LGslice.cb3504eb.mp4
607.67400031909
1204.5559999533
0
0
-1
Media
https://www.google.com/pagead/1p-user-list/365421231/?random=1627694241086&cv=9&fst=1627693200000&num=1&bg=ffffff&guid=ON&eid=376635471&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&gtm=2oa7s0&sendb=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fcandy.com%2F&tiba=CANDY%3A%20A%20Digital%20Collectible%20Experience&async=1&fmt=3&is_vtc=1&random=3783820514&resp=GooglemKTybQhCsO&rmt_tld=0&ipr=y
h2
621.46100029349
630.77099993825
763
42
200
image/gif
Image
https://bid.g.doubleclick.net/xbbe/pixel?d=KAE
h2
1211.570000276
1218.005000148
984
0
200
text/html
Document
https://www.facebook.com/tr/?id=320087963089791&ev=PageView&dl=https%3A%2F%2Fcandy.com%2F%23%2F&rl=&if=false&ts=1627694241743&sw=800&sh=600&v=2.9.44&r=stable&ec=1&o=30&fbp=fb.1.1627694241112.26873357&it=1627694240820&coo=false&rqm=GET
h2
1213.3630001917
1228.5700002685
478
44
200
image/gif
Image
https://www.facebook.com/tr/?id=320087963089791&ev=Microdata&dl=https%3A%2F%2Fcandy.com%2F%23%2F&rl=&if=false&ts=1627694242619&cd[DataLayer]=%5B%5D&cd[Meta]=%7B%22title%22%3A%22CANDY%3A%20A%20Digital%20Collectible%20Experience%22%2C%22meta%3Adescription%22%3A%22Crave.%20Collect.%20Connect.%20Being%20a%20true%20fan%20is%20no%20longer%20just%20a%20spectator%20sport.%22%7D&cd[OpenGraph]=%7B%7D&cd[Schema.org]=%5B%5D&cd[JSON-LD]=%5B%5D&sw=800&sh=600&v=2.9.44&r=stable&ec=2&o=30&fbp=fb.1.1627694241112.26873357&it=1627694240820&coo=false&es=automatic&tm=3&rqm=GET
h2
2090.7499999739
2106.7530000582
478
44
200
image/gif
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-8C9XEDS6Q6&gtm=2oe7s0&_p=258255835&sr=800x600&ul=en-us&cid=602551808.1627694241&_s=2&dl=https%3A%2F%2Fcandy.com%2F&dt=CANDY%3A%20A%20Digital%20Collectible%20Experience&sid=1627694240&sct=1&seg=0&en=scroll&_et=981&epn.percent_scrolled=90
6221.1710000411
6223.1960003264
0
0
-1
Ping
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)
149.358
10.636
161.688
5.102
203.593
16.842
221.504
28.891
281.545
19.935
303.467
26.29
333.232
182.263
515.515
14.917
532.443
24.716
562.169
7.142
569.344
25.369
594.727
8.714
603.452
9.083
648.233
51.699
1216.731
6.074
1230.036
7.001
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.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.1 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 180 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Opportunities

Properly size images — Potential savings of 225 KiB
Images can slow down the page's load time. Candy.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://candy.com/static/media/statics_SF_H4k.158e0b98.png
284079
230258
Reduce unused JavaScript — Potential savings of 153 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://candy.com/static/js/2.d26960df.chunk.js
147177
73108
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
74482
55941
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
62948
27127
Serve images in next-gen formats — Potential savings of 274 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://candy.com/static/media/statics_SF_H4k.158e0b98.png
284079
216393
https://candy.com/static/media/statics_SF_H1080.68e5c671.png
87956
56072
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
87786
8262

Metrics

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

Diagnostics

Serve static assets with an efficient cache policy — 14 resources found
Candy.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://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
1200000
74482
https://connect.facebook.net/en_US/fbevents.js
1200000
26621
https://candy.com/static/media/LadRing564x638.410e70b4.mp4
14400000
6822229
https://candy.com/static/media/SF_CandyBlink.242cf303.mp4
14400000
4328246
https://candy.com/static/media/BlackC-1080.66f04aba.mp4
14400000
3720804
https://candy.com/static/media/statics_SF_H4k.158e0b98.png
14400000
285120
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
14400000
273613
https://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
14400000
233627
https://candy.com/static/js/2.d26960df.chunk.js
14400000
147177
https://candy.com/static/media/statics_SF_H1080.68e5c671.png
14400000
88988
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
14400000
88823
https://candy.com/static/js/main.09495500.chunk.js
14400000
64853
https://candy.com/static/media/statics_LAD_1080.8486f87b.png
14400000
38972
https://candy.com/static/css/main.475b7c0f.chunk.css
14400000
1432
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://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
101.73399979249
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
77.372999861836
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://candy.com/static/media/statics_SF_H4k.158e0b98.png
img
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of candy.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.
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>`, `<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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-pure@3.0.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://candy.com/static/js/main.09495500.chunk.js
https://candy.com/static/js/main.09495500.chunk.js.map
https://candy.com/static/js/2.d26960df.chunk.js
https://candy.com/static/js/2.d26960df.chunk.js.map
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://candy.com/
Allowed

Audits

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
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_CONNECTION_FAILED
91

SEO

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

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img

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

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 candy.com. This includes details about web app manifests.

Installable

Web app manifest and service worker 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.

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.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is 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 candy.com on mobile screens.
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.

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.
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) 76
Performance 42
Accessibility 90
Best Practices 87
SEO 80
Progressive Web App 83
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://candy.com/
Updated: 31st July, 2021

2.18 seconds
First Contentful Paint (FCP)
66%
21%
13%

0.02 seconds
First Input Delay (FID)
96%
2%
2%

Simulate loading on mobile
42

Performance

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

Metrics

Total Blocking Time — 200 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).

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Candy.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Candy.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Candy.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Candy.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Candy.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 8 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://candy.com/static/media/statics_LAD_4k.196a31fd.png
87786
8262
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 30 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://candy.com/
31.463
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Candy.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://candy.com/
630
https://candy.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Candy.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 — Potential savings of 12 KiB
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.
URL Potential Savings (Bytes)
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
11816
https://candy.com/static/js/2.d26960df.chunk.js
127
https://connect.facebook.net/en_US/fbevents.js
45
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
0

Diagnostics

Avoids enormous network payloads — Total size was 1,057 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
273607
https://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
233631
https://candy.com/static/js/2.d26960df.chunk.js
147167
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
88829
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
74700
https://candy.com/static/js/main.09495500.chunk.js
64857
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
62948
https://www.googletagmanager.com/gtag/js?id=AW-365421231&l=dataLayer&cx=c
39509
https://candy.com/static/media/statics_LAD_1080.8486f87b.png
38976
https://connect.facebook.net/en_US/fbevents.js
27362
Avoids an excessive DOM size — 46 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
46
Maximum DOM Depth
10
Maximum Child Elements
9
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Candy.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Keep request counts low and transfer sizes small — 28 requests • 15,429 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
28
15799202
Media
3
14716866
Font
2
507238
Script
11
439073
Image
6
130366
Document
1
3053
Stylesheet
1
1430
Other
4
1176
Third-party
16
229993
Minimize third-party usage — Third-party code blocked the main thread for 200 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)
102457
148.508
103165
56.456
16601
0
5929
0
763
0
383
0
0
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.13671644313299
0.13239908177089
div
0.080940742998417
0.078371195601642
div
0.020938985216361
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 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://candy.com/static/js/2.d26960df.chunk.js
8010
324
https://candy.com/
1218
183
https://candy.com/static/js/2.d26960df.chunk.js
7260
179
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
3376
147
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
4272
126
https://www.googletagmanager.com/gtag/js?id=AW-365421231&l=dataLayer&cx=c
4423
119
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
3299
77
https://connect.facebook.net/en_US/fbevents.js
2399
73
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

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://candy.com/
http/1.1
0
69.89100005012
793
0
301
https://candy.com/
h2
70.551000069827
101.01600002963
3053
4710
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
h2
118.0840000743
146.26100007445
62948
166593
200
application/javascript
Script
https://platform.twitter.com/oct.js
http/1.1
118.43300005421
183.7270000251
383
0
301
https://candy.com/static/css/main.475b7c0f.chunk.css
h2
118.65100008436
177.65700002201
1430
872
200
text/css
Stylesheet
https://candy.com/static/js/2.d26960df.chunk.js
h2
119.07400004566
192.39400001243
147167
526563
200
application/javascript
Script
https://candy.com/static/js/main.09495500.chunk.js
h2
119.41300006583
148.57299998403
64857
103539
200
application/javascript
Script
https://connect.facebook.net/en_US/fbevents.js
h2
226.9250000827
244.95600000955
27362
100785
200
application/x-javascript
Script
https://static.ads-twitter.com/oct.js
h2
184.4239999773
205.32100007404
2480
5160
200
application/javascript
Script
https://www.google-analytics.com/g/collect?v=2&tid=G-8C9XEDS6Q6&gtm=2oe7s0&_p=1915390898&sr=360x640&ul=en-us&cid=722447783.1627694291&_s=1&dl=https%3A%2F%2Fcandy.com%2F&dt=CANDY%3A%20A%20Digital%20Collectible%20Experience&sid=1627694291&sct=1&seg=0&en=page_view&_fv=1&_nsi=1&_ss=1
218.13900000416
223.98400004022
0
0
-1
Ping
https://www.googletagmanager.com/gtag/js?id=AW-365421231&l=dataLayer&cx=c
h2
228.30499999691
244.14900003467
39509
97610
200
application/javascript
Script
https://static.ads-twitter.com/uwt.js
h2
228.49100001622
254.07400005497
2479
5160
200
application/javascript
Script
https://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
h2
383.82500002626
418.4360000072
233631
232576
200
binary/octet-stream
Font
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
h2
384.36300004832
445.38400007877
273607
272560
200
binary/octet-stream
Font
https://candy.com/static/media/statics_LAD_1080.8486f87b.png
h2
405.14200006146
434.37500006985
38976
37939
200
image/png
Image
data
405.18000000156
405.31400009058
0
2952
200
image/png
Image
data
405.66799999215
405.77299997676
0
3629
200
image/png
Image
data
406.04800009169
406.16900008172
0
4847
200
image/png
Image
data
406.43600001931
406.55900002457
0
4400
200
image/png
Image
data
408.29300007317
408.52900000755
0
9958
200
image/png
Image
data
408.89299998526
409.04400008731
0
5087
200
image/png
Image
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
h2
409.92100001313
435.1279999828
88829
87786
200
image/png
Image
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
h2
485.42500007898
546.07100004796
74700
258708
200
application/x-javascript
Script
https://www.googleadservices.com/pagead/conversion_async.js
h2
504.75600000937
515.51400008611
14653
36573
200
text/javascript
Script
https://candy.com/static/media/BlackC-1080.66f04aba.mp4
h2
543.07600005995
631.28200010397
3720800
3145728
206
video/mp4
Media
https://candy.com/static/media/SF_CandyBlink.242cf303.mp4
h2
544.74400007166
645.00700007193
4328234
3145728
206
video/mp4
Media
https://candy.com/static/media/LadRing1080x1000.8d68937a.mp4
h2
546.7930000741
715.90000006836
6667832
3145728
206
video/mp4
Media
https://t.co/i/adsct?type=javascript&version=2.0.1&p_id=Twitter&p_user_id=0&txn_id=o646q&events=%5B%5B%22pageview%22%2Cnull%5D%5D&tw_sale_amount=0&tw_order_quantity=0&tw_iframe_status=0&tw_document_href=https%3A%2F%2Fcandy.com%2F%23%2F
h2
561.36300007347
594.77500000503
695
43
200
image/gif
Image
https://googleads.g.doubleclick.net/pagead/viewthroughconversion/365421231/?random=1627694291621&cv=9&fst=1627694291621&num=1&bg=ffffff&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=24&u_his=2&u_tz=-420&u_java=false&u_nplug=0&u_nmime=0&gtm=2oa7s0&sendb=1&ig=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fcandy.com%2F&tiba=CANDY%3A%20A%20Digital%20Collectible%20Experience&hn=www.googleadservices.com&async=1&rfmt=3&fmt=4
h2
582.06400007475
592.64000004623
1948
1632
200
text/javascript
Script
https://www.facebook.com/tr/?id=320087963089791&ev=PageView&dl=https%3A%2F%2Fcandy.com%2F%23%2F&rl=&if=false&ts=1627694291751&sw=360&sh=640&v=2.9.44&r=stable&ec=0&o=30&fbp=fb.1.1627694291748.2136562672&it=1627694291527&coo=false&rqm=GET
h2
725.47800000757
742.81900003552
625
44
200
image/gif
Image
https://www.google.com/pagead/1p-user-list/365421231/?random=1627694291621&cv=9&fst=1627693200000&num=1&bg=ffffff&guid=ON&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=24&u_his=2&u_tz=-420&u_java=false&u_nplug=0&u_nmime=0&gtm=2oa7s0&sendb=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fcandy.com%2F&tiba=CANDY%3A%20A%20Digital%20Collectible%20Experience&async=1&fmt=3&is_vtc=1&random=1539308538&resp=GooglemKTybQhCsO&rmt_tld=0&ipr=y
h2
728.64400001708
737.18500009272
763
42
200
image/gif
Image
https://analytics.twitter.com/i/adsct?type=javascript&version=2.0.1&p_id=Twitter&p_user_id=0&txn_id=o646q&events=%5B%5B%22pageview%22%2Cnull%5D%5D&tw_sale_amount=0&tw_order_quantity=0&tw_iframe_status=0&tpx_cb=twttr.conversion.loadPixels&tw_document_href=https%3A%2F%2Fcandy.com%2F%23%2F
h2
746.67100002989
789.16799998842
970
31
200
application/javascript
Script
https://www.facebook.com/tr/?id=320087963089791&ev=Microdata&dl=https%3A%2F%2Fcandy.com%2F%23%2F&rl=&if=false&ts=1627694293255&cd[DataLayer]=%5B%5D&cd[Meta]=%7B%22title%22%3A%22CANDY%3A%20A%20Digital%20Collectible%20Experience%22%2C%22meta%3Adescription%22%3A%22Crave.%20Collect.%20Connect.%20Being%20a%20true%20fan%20is%20no%20longer%20just%20a%20spectator%20sport.%22%7D&cd[OpenGraph]=%7B%7D&cd[Schema.org]=%5B%5D&cd[JSON-LD]=%5B%5D&sw=360&sh=640&v=2.9.44&r=stable&ec=1&o=30&fbp=fb.1.1627694291748.2136562672&it=1627694291527&coo=false&es=automatic&tm=3&rqm=GET
h2
2212.2130000498
2228.6249999888
478
44
200
image/gif
Image
https://www.google-analytics.com/g/collect?v=2&tid=G-8C9XEDS6Q6&gtm=2oe7s0&_p=1915390898&sr=360x640&ul=en-us&cid=722447783.1627694291&_s=2&dl=https%3A%2F%2Fcandy.com%2F&dt=CANDY%3A%20A%20Digital%20Collectible%20Experience&sid=1627694291&sct=1&seg=0&en=scroll&_et=538&epn.percent_scrolled=90
5757.4160000077
5759.0320000891
0
0
-1
Ping
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)
133.201
10.336
191.759
19.265
212.517
36.803
278.609
162.185
447.535
44.656
495.466
18.249
513.766
29.685
543.718
14.359
559.716
11.496
600.506
9.887
610.507
91.485
705.675
31.534
780.135
5.002
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.

Metrics

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

Opportunities

Properly size images — Potential savings of 70 KiB
Images can slow down the page's load time. Candy.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
87786
71248

Diagnostics

Reduce JavaScript execution time — 1.5 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://candy.com/static/js/main.09495500.chunk.js
586.792
509.808
6.336
https://candy.com/
533.396
15.692
8.996
Unattributable
358.508
1.912
0
https://candy.com/static/js/2.d26960df.chunk.js
349.828
282.74
35.404
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
283.96
252.036
20.444
https://www.googletagmanager.com/gtag/js?id=AW-365421231&l=dataLayer&cx=c
145.292
131.816
10.04
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
142.408
111.908
22.112
https://connect.facebook.net/en_US/fbevents.js
73.652
63.564
7.224
Minimize main-thread work — 2.5 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
1396.604
Other
456.252
Rendering
383.64
Style & Layout
132.228
Script Parsing & Compilation
121.124
Parse HTML & CSS
26.8

Metrics

First Contentful Paint — 4.9 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 9.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 7.7 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.449
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 320 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 4.9 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 10284 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Reduce unused JavaScript — Potential savings of 152 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://candy.com/static/js/2.d26960df.chunk.js
147167
72487
https://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
74700
56105
https://www.googletagmanager.com/gtag/js?id=G-8C9XEDS6Q6
62948
27127

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Candy.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://connect.facebook.net/signals/config/320087963089791?v=2.9.44&r=stable
1200000
74700
https://connect.facebook.net/en_US/fbevents.js
1200000
27362
https://candy.com/static/media/LadRing1080x1000.8d68937a.mp4
14400000
6667832
https://candy.com/static/media/SF_CandyBlink.242cf303.mp4
14400000
4328234
https://candy.com/static/media/BlackC-1080.66f04aba.mp4
14400000
3720800
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
14400000
273607
https://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
14400000
233631
https://candy.com/static/js/2.d26960df.chunk.js
14400000
147167
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
14400000
88829
https://candy.com/static/js/main.09495500.chunk.js
14400000
64857
https://candy.com/static/media/statics_LAD_1080.8486f87b.png
14400000
38976
https://candy.com/static/css/main.475b7c0f.chunk.css
14400000
1430
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://candy.com/static/media/SuisseIntl-SemiBold.3d5355df.ttf
34.610999980941
https://candy.com/static/media/SuisseIntl-Regular.dcf968b3.ttf
61.021000030451
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://candy.com/static/media/statics_LAD_4k.196a31fd.png
img
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of candy.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.
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>`, `<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.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
React
core-js
core-js-pure@3.0.0
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.
URL Map URL
https://candy.com/static/js/main.09495500.chunk.js
https://candy.com/static/js/main.09495500.chunk.js.map
https://candy.com/static/js/2.d26960df.chunk.js
https://candy.com/static/js/2.d26960df.chunk.js.map
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://candy.com/
Allowed

Audits

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
80

SEO

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

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.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img

Mobile Friendly

Document doesn't use legible font sizes — 0% 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
.glZmJR
67.12%
6.12px
.jIfccS
19.86%
5.4px
.oxVOu
13.01%
11.16px
Tap targets are not sized appropriately — 50% 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
15x5
15x5

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

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 candy.com. This includes details about web app manifests.

Installable

Web app manifest and service worker 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.

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.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is 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 candy.com on mobile screens.
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.

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.
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: 104.21.20.180
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
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.54.219.124
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.candy.com
Issued By: R3
Valid From: 26th July, 2021
Valid To: 24th October, 2021
Subject: CN = *.candy.com
Hash: 3046ea92
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03F2D5D6E3A626188495C0A4EAF93A8BA040
Serial Number (Hex): 03F2D5D6E3A626188495C0A4EAF93A8BA040
Valid From: 26th July, 2024
Valid To: 24th October, 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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Jul 26 18:38:55.533 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C4:75:3D:21:9F:FA:E6:1F:C3:C5:1F:
B0:2B:D8:38:DD:A3:B2:AB:52:3D:F8:EF:C7:14:E1:A8:
78:B5:6E:68:AC:02:21:00:91:30:FE:0E:E3:B7:72:EB:
E9:A2:54:49:2C:C8:57:A3:6A:72:3D:32:70:9A:B9:19:
66:6D:C6:DB:78:9F:EA:CB
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Jul 26 18:38:55.571 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:DB:C2:0C:12:9C:9F:A8:33:F8:3B:D2:
0F:53:47:7A:CE:57:34:62:6E:E3:2B:CD:A0:BA:B3:60:
AE:5C:75:D7:1E:02:21:00:FC:E1:9F:4E:51:FB:77:82:
0B:0E:5E:11:54:36:E0:09:C3:DE:96:A1:1F:71:EE:3E:
29:A0:01:FF:66:64:C1:B6
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:candy.com
DNS:*.candy.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 31st July, 2021
Content-Type: text/html
Cache-Control: max-age=14400
Server: cloudflare
Connection: keep-alive
Last-Modified: 28th July, 2021
X-Cache: Hit from cloudfront
Via: 1.1 c1e4a92dc10823ce70a0466c21ad9e1f.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ATL51-C1
X-Amz-Cf-Id: CsoXR7um8HNZbmuvSLVpvb-l8ARXmLL38PsIu02HXEhu0k8xGOUlrw==
Age: 4349
CF-Cache-Status: HIT
Accept-Ranges: bytes
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=R%2BjFRzaABWVgCXWVJWMUkx7raIYvtYfIHplf8Uhjy%2BhyLHBN3wRbPUZG3yOEYrIUvWHMTN5dPAPydBb6XnR1yPuD1nSDoYWS9Q60IVgfX0PznA5oVzL%2BtPjw3Yo%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
CF-RAY: 6772fc66aff819ff-EWR
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400

Whois Lookup

Created: 17th August, 1994
Changed: 28th May, 2021
Expires: 2nd October, 2028
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: edward.ns.cloudflare.com
thea.ns.cloudflare.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: candy.com@domainsbyproxy.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: candy.com@domainsbyproxy.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: candy.com@domainsbyproxy.com
Full Whois: Domain Name: candy.com
Registry Domain ID: 5286674_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2021-05-28T11:34:44Z
Creation Date: 1994-08-17T23:00:00Z
Registrar Registration Expiration Date: 2028-10-02T12:36:37Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.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: candy.com@domainsbyproxy.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: candy.com@domainsbyproxy.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: candy.com@domainsbyproxy.com
Name Server: EDWARD.NS.CLOUDFLARE.COM
Name Server: THEA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-07-31T01:17:17Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

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
edward.ns.cloudflare.com 172.64.35.210
thea.ns.cloudflare.com 108.162.194.247
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,029 USD 2/5
0/5
$35,876 USD 3/5
$445 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$1,013 USD 1/5
$102 USD
$2,255 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$1,027 USD 1/5