grandevegascasino.com

grandevegascasino.com is SSL secured

Free website and domain report on grandevegascasino.com

Last Updated: 19th November, 2022 Update Now
Overview

Snoop Summary for grandevegascasino.com

This is a free and comprehensive report about grandevegascasino.com. The domain grandevegascasino.com is currently hosted on a server located in United States with the IP address 104.18.9.124, where the local currency is USD and English is the local language. Grandevegascasino.com has the potential to be earning an estimated $4 USD per day from advertising revenue. If grandevegascasino.com was to be sold it would possibly be worth $3,149 USD (based on the daily revenue potential of the website over a 24 month period). Grandevegascasino.com is quite popular with an estimated 1,509 daily unique visitors. This report was last updated 19th November, 2022.

About grandevegascasino.com

Site Preview: grandevegascasino.com grandevegascasino.com
Title: Grande Vegas Online Casino - Get a $300 Bonus with $50 FREE
Description: 96% of USA players prefer playing at an online casino. Play at the best - Grande Vegas Online Casino where new players get $300 FREE PLUS 50 FREE SPINS.
Keywords and Tags: gambling, popular
Related Terms: 300 cast, airbus a330 300, ariana grande ethnicity, bunda grande, eq2 players, grande distribuzione, grande formato, grande segredo da gordura, how tall is ariana grande, la grande librairie
Fav Icon:
Age: Over 15 years old
Domain Created: 1st December, 2008
Domain Updated: 1st December, 2021
Domain Expires: 1st December, 2023
Review

Snoop Score

2/5

Valuation

$3,149 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 544,000
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: 1,509
Monthly Visitors: 45,929
Yearly Visitors: 550,785
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $131 USD
Yearly Revenue: $1,570 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: grandevegascasino.com 21
Domain Name: grandevegascasino 17
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.05 seconds
Load Time Comparison: Faster than 41% of sites

PageSpeed Insights

Avg. (All Categories) 79
Performance 97
Accessibility 94
Best Practices 67
SEO 83
PWA 56
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.grandevegascasino.com/
Updated: 19th November, 2022

2.24 seconds
First Contentful Paint (FCP)
70%
13%
17%

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

Simulate loading on desktop
97

Performance

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

Metrics

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

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://grandevegascasino.com/
http/1.1
0
1443.284999812
396
0
301
text/html
https://grandevegascasino.com/
http/1.1
1443.5699998867
1526.1369999498
325
0
301
text/plain
https://www.grandevegascasino.com/
h2
1526.4019998722
1645.7109998446
11260
37041
200
text/html
Document
https://www.grandevegascasino.com/images/blank.png
h2
1651.5799998306
9750.8709998801
580
70
200
image/webp
Image
https://www.grandevegascasino.com/images/homepage/winners.png
h2
1651.7699998803
1722.6569999475
2114
1594
200
image/webp
Image
https://www.grandevegascasino.com/images/homepage/teaser-bg-home.jpg
h2
1660.8259999193
1744.888999965
39951
39412
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/06_SupportIcon.png
h2
1660.9029998071
1723.868999863
912
386
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/05_BankingIcon.png
h2
1661.0169999767
1731.2939998228
1071
544
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/04_VIPIcon.png
h2
1661.1859998666
1731.0709999874
795
274
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/03_TournamentIcon.png
h2
1661.3559999969
1733.1719999202
788
260
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/02_GamesIcon.png
h2
1661.4599998575
1702.2119998001
919
394
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/01_PromoIcon.png
h2
1661.5959999617
1706.5699999221
930
406
200
image/webp
Image
https://www.grandevegascasino.com/images/home.png
h2
1661.6879999638
1727.9169999529
616
100
200
image/webp
Image
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
h2
1653.2969998661
1754.9579998013
22667
145113
200
text/css
Stylesheet
https://www.grandevegascasino.com/templates/grandevegas/css/template.min.css?18e5a32dea5eadd1a93d1898d7223326
h2
1653.5519999452
1735.9960000031
8968
62740
200
text/css
Stylesheet
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/41d767471fb5e12a73a715c4061788addbd8bf165fa67b1a41564e35dbe7cb9f.css
h2
1653.762999922
1699.4549999945
13103
58744
200
text/css
Stylesheet
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde8241fbdf3bf473e281260b5b7cc87a9.js
h2
1661.8029999081
1750.6469998043
39290
108483
200
text/javascript
Script
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
h2
1661.9589999318
1757.1039998438
64540
253540
200
text/javascript
Script
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd0f0101442216280a2a1ee3de12923b29.js
h2
1662.0539999567
1723.1919998303
3540
9913
200
text/javascript
Script
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
h2
1662.1369998902
1734.6309998538
4154
8430
200
text/javascript
Script
data
1666.1749999039
1666.2679999135
0
67
200
image/svg+xml
Image
https://www.grandevegascasino.com/templates/grandevegas/fonts/CabinCondensed-Regular.woff2
h2
1744.754999876
1781.6190000158
36446
36020
200
application/x-font-woff2
Font
https://www.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
h2
1745.2909999993
1784.6140000038
74746
74320
200
application/x-font-woff2
Font
https://chat.grandevegascasino.com/lhc_web/index.php/chat/getstatus/(click)/internal/(position)/bottom_right/(ma)/br/(check_operator_messages)/true/(top)/350/(units)/pixels/(leaveamessage)/true/(department)/22/(theme)/23?r=&l=%2F%2Fwww.grandevegascasino.com%2F
h2
1878.5529998131
2278.3239998389
2008
4121
200
text/javascript
Script
https://track.grandevegascasino.com/js/container_hDwedm6V.js
http/1.1
1879.2119999416
2179.3079997879
66501
237976
200
application/javascript
Script
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
h2
1879.2879998218
1978.9049997926
40914
225312
200
application/javascript
Script
https://www.grandevegascasino.com/images/logo.png
h2
1907.1029999759
1937.3889998533
6910
6392
200
image/webp
Image
https://www.grandevegascasino.com/images/separator.png
h2
1907.3520000093
1937.0069999713
2033
1510
200
image/webp
Image
https://www.grandevegascasino.com/images/home-teaser.png
1907.0199998096
11776.7419999
0
0
-1
Image
https://www.grandevegascasino.com/modules/mod_gamesfp/helper.php
h2
1910.9029998071
6933.8239999488
508
338
411
text/html
XHR
https://secure.cdnserve.in/grandevegas/en/api/bigwinners/50
1916.1099998746
11807.941999985
0
0
-1
XHR
https://track.grandevegascasino.com/matomo.js
http/1.1
2200.5099998787
2494.3769997917
49238
166397
200
application/javascript
Script
https://kbiy2d6wh8.a2btest.com/kameleoon.js
2200.8799999021
12086.657000007
0
0
-1
Script
https://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
h2
2281.1629998032
2361.5180000197
24362
88192
200
application/javascript
Script
https://track.grandevegascasino.com/matomo.php?action_name=www.grandevegascasino.com%2FGrande%20Vegas%20Online%20Casino%20-%20Get%20a%20%24300%20Bonus%20with%20%2450%20FREE&idsite=17&rec=1&r=581532&h=15&m=45&s=20&url=https%3A%2F%2Fwww.grandevegascasino.com%2F&_id=5ee6afb6fbbf4704&_idn=1&send_image=0&_refts=0&cookie=1&res=800x600&pv_id=f58Th8&pf_net=0&pf_srv=120&pf_tfr=0&pf_dm1=19&uadata=%7B%22fullVersionList%22%3A%5B%5D%2C%22mobile%22%3Afalse%2C%22model%22%3A%22%22%2C%22platform%22%3A%22macOS%22%2C%22platformVersion%22%3A%2210.15.7%22%7D
2522.4109999835
2523.9039999433
0
0
-1
Ping
https://track.grandevegascasino.com/plugins/HeatmapSessionRecording/configs.php?idsite=17&trackerid=XEDQKT&url=https%3A%2F%2Fwww.grandevegascasino.com%2F
http/1.1
2530.436999863
2688.9869999141
470
117
200
application/javascript
Script
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)
1648.716
11.661
1740.379
27.879
1773.804
28.819
1803.668
12.566
1816.79
62.494
1886.354
21.948
1908.339
9.539
1947.108
33.512
2063.744
16.485
2192.462
10.678
2504.214
17.008
9757.684
7.951
11787.61
6.195
12087.872
10.978
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources — Potential savings of 40 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Grandevegascasino.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
22667
80
Properly size images
Images can slow down the page's load time. Grandevegascasino.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Grandevegascasino.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Grandevegascasino.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Grandevegascasino.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 34 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Grandevegascasino.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
22667
21759
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/41d767471fb5e12a73a715c4061788addbd8bf165fa67b1a41564e35dbe7cb9f.css
13103
13103
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 120 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://www.grandevegascasino.com/
120.305
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Grandevegascasino.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 0 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://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
46
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
43
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 509 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
74746
https://track.grandevegascasino.com/js/container_hDwedm6V.js
66501
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
64540
https://track.grandevegascasino.com/matomo.js
49238
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
40914
https://www.grandevegascasino.com/images/homepage/teaser-bg-home.jpg
39951
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde8241fbdf3bf473e281260b5b7cc87a9.js
39290
https://www.grandevegascasino.com/templates/grandevegas/fonts/CabinCondensed-Regular.woff2
36446
https://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
24362
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
22667
Avoids an excessive DOM size — 394 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
394
Maximum DOM Depth
11
Maximum Child Elements
15
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Grandevegascasino.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.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.grandevegascasino.com/
126.818
5.842
1.364
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
66.052
7.706
0.225
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
65.844
15.136
3.073
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)
Other
134.748
Script Evaluation
93.319
Style & Layout
71.642
Rendering
57.477
Script Parsing & Compilation
16.874
Parse HTML & CSS
12.895
Garbage Collection
1.815
Keep request counts low and transfer sizes small — 35 requests • 509 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
35
521055
Script
11
295017
Font
2
111192
Image
13
57619
Stylesheet
3
44738
Document
1
11260
Other
5
1229
Media
0
0
Third-party
3
40914
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0071036183611148
0.0060980833419616
0.0058753519291169
0.0043925662030236
0.001773201539152
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
931
62
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 grandevegascasino.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

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

Other

Reduce unused JavaScript — Potential savings of 181 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://track.grandevegascasino.com/js/container_hDwedm6V.js
66501
52420
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
64540
49004
https://track.grandevegascasino.com/matomo.js
49238
32848
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
40914
27366
https://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
24362
23902
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Grandevegascasino.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://grandevegascasino.com/
190
https://grandevegascasino.com/
150
https://www.grandevegascasino.com/
0

Other

Serve static assets with an efficient cache policy — 19 resources found
Grandevegascasino.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://track.grandevegascasino.com/js/container_hDwedm6V.js
0
66501
https://track.grandevegascasino.com/matomo.js
0
49238
https://track.grandevegascasino.com/plugins/HeatmapSessionRecording/configs.php?idsite=17&trackerid=XEDQKT&url=https%3A%2F%2Fwww.grandevegascasino.com%2F
0
470
https://www.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
86400000
74746
https://www.grandevegascasino.com/images/homepage/teaser-bg-home.jpg
86400000
39951
https://www.grandevegascasino.com/templates/grandevegas/fonts/CabinCondensed-Regular.woff2
86400000
36446
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
86400000
22667
https://www.grandevegascasino.com/templates/grandevegas/css/template.min.css?18e5a32dea5eadd1a93d1898d7223326
86400000
8968
https://www.grandevegascasino.com/images/logo.png
86400000
6910
https://www.grandevegascasino.com/images/homepage/winners.png
86400000
2114
https://www.grandevegascasino.com/images/separator.png
86400000
2033
https://www.grandevegascasino.com/images/icons/05_BankingIcon.png
86400000
1071
https://www.grandevegascasino.com/images/icons/01_PromoIcon.png
86400000
930
https://www.grandevegascasino.com/images/icons/02_GamesIcon.png
86400000
919
https://www.grandevegascasino.com/images/icons/06_SupportIcon.png
86400000
912
https://www.grandevegascasino.com/images/icons/04_VIPIcon.png
86400000
795
https://www.grandevegascasino.com/images/icons/03_TournamentIcon.png
86400000
788
https://www.grandevegascasino.com/images/home.png
86400000
616
https://www.grandevegascasino.com/images/blank.png
86400000
580
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.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
39.323000004515
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
https://www.grandevegascasino.com/images/logo.png
https://www.grandevegascasino.com/images/separator.png
https://www.grandevegascasino.com/images/separator.png
https://www.grandevegascasino.com/images/homepage/winners.png
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of grandevegascasino.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 `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

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

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"]`
Grandevegascasino.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

Contrast

Names and labels

Links do not 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.

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
Isotope
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.
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://grandevegascasino.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.grandevegascasino.com/images/blank.png
55 x 50
1 x 1
55 x 50

Audits

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_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: the server responded with a status of 411 (Length Required)
83

SEO

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

Content Best Practices

Links do not have descriptive text — 4 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of grandevegascasino.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

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

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 provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

2.50 seconds
First Contentful Paint (FCP)
65%
15%
20%

0.22 seconds
First Input Delay (FID)
68%
9%
23%

Simulate loading on mobile
65

Performance

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

Metrics

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).
Cumulative Layout Shift — 0.054
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Grandevegascasino.com should consider serving more appropriate-sized images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Grandevegascasino.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Grandevegascasino.com should consider minifying JS files.
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 70 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://www.grandevegascasino.com/
67.073
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Grandevegascasino.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 0 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://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
46
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
43
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 541 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
74746
https://track.grandevegascasino.com/js/container_hDwedm6V.js
66501
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
64540
https://track.grandevegascasino.com/matomo.js
49237
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
40914
https://www.grandevegascasino.com/images/homepage/teaser-bg-home.jpg
39952
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde8241fbdf3bf473e281260b5b7cc87a9.js
39290
https://www.grandevegascasino.com/templates/grandevegas/fonts/CabinCondensed-Regular.woff2
36446
https://www.grandevegascasino.com/images/Blog/bitcoin.jpg
32664
https://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
24362
Avoids an excessive DOM size — 394 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
394
Maximum DOM Depth
11
Maximum Child Elements
15
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Grandevegascasino.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.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.grandevegascasino.com/
967.264
24.32
5.756
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
370.756
63.212
1.556
Unattributable
226.86
19.036
0
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde8241fbdf3bf473e281260b5b7cc87a9.js
166.596
135.648
7.404
https://track.grandevegascasino.com/matomo.js
108.684
94.78
12.916
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
96.192
79.012
16.016
https://track.grandevegascasino.com/js/container_hDwedm6V.js
61.952
41.532
18.5
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
50.104
30.372
19.152
Keep request counts low and transfer sizes small — 36 requests • 541 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
36
553716
Script
11
295016
Font
2
111192
Image
14
90285
Stylesheet
3
44734
Document
1
11260
Other
5
1229
Media
0
0
Third-party
3
40914
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.01874449614277
0.01419046419399
0.011112508898958
0.0089571015125185
0.00082208601456115
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://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde8241fbdf3bf473e281260b5b7cc87a9.js
3179
232
https://track.grandevegascasino.com/matomo.js
6227
98
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
3090
89
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
3411
84
https://www.grandevegascasino.com/
1954
71
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
6325
66
https://www.grandevegascasino.com/
1890
58
https://track.grandevegascasino.com/js/container_hDwedm6V.js
5391
56
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 grandevegascasino.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Audits

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://grandevegascasino.com/
http/1.1
0
1381.4489999786
396
0
301
text/html
https://grandevegascasino.com/
http/1.1
1381.8510002457
1488.6050000787
325
0
301
text/plain
https://www.grandevegascasino.com/
h2
1488.9699998312
1555.0520000979
11260
37041
200
text/html
Document
https://www.grandevegascasino.com/images/blank.png
h2
1565.4830001295
1597.6220001467
581
70
200
image/webp
Image
https://www.grandevegascasino.com/images/homepage/winners.png
h2
1565.7730000094
1601.9569998607
2114
1594
200
image/webp
Image
https://www.grandevegascasino.com/images/homepage/teaser-bg-home.jpg
h2
1575.1780001447
1608.9699999429
39952
39412
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/06_SupportIcon.png
h2
1575.4269999452
1605.8869999833
912
386
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/05_BankingIcon.png
h2
1577.0370000973
1617.1039999463
1071
544
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/04_VIPIcon.png
h2
1577.2730000317
1614.1599998809
795
274
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/03_TournamentIcon.png
h2
1577.4220000021
1613.2689998485
788
260
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/02_GamesIcon.png
h2
1577.8660001233
1610.5320001952
919
394
200
image/webp
Image
https://www.grandevegascasino.com/images/icons/01_PromoIcon.png
h2
1578.3359999768
1615.8580002375
930
406
200
image/webp
Image
https://www.grandevegascasino.com/images/home.png
h2
1578.7760000676
1609.8739998415
616
100
200
image/webp
Image
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
h2
1567.1379999258
1622.1940000542
22667
145113
200
text/css
Stylesheet
https://www.grandevegascasino.com/templates/grandevegas/css/template.min.css?18e5a32dea5eadd1a93d1898d7223326
h2
1567.3650000244
4372.5109999068
8964
62740
200
text/css
Stylesheet
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/41d767471fb5e12a73a715c4061788addbd8bf165fa67b1a41564e35dbe7cb9f.css
h2
1567.7010002546
1613.7859998271
13103
58744
200
text/css
Stylesheet
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde8241fbdf3bf473e281260b5b7cc87a9.js
h2
1579.0679999627
1640.6910000369
39290
108483
200
text/javascript
Script
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
h2
1579.3240000494
1630.4879998788
64540
253540
200
text/javascript
Script
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd0f0101442216280a2a1ee3de12923b29.js
h2
1579.5089998282
1609.4340002164
3540
9913
200
text/javascript
Script
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bde4555fb9988be61f335d0f278cd10b8c.js
h2
1579.7560000792
1656.5970000811
4154
8430
200
text/javascript
Script
data
1580.9039999731
1580.9920001775
0
67
200
image/svg+xml
Image
https://www.grandevegascasino.com/images/Blog/bitcoin.jpg
h2
1706.3750000671
1743.7320002355
32664
32168
200
image/jpeg
Image
https://chat.grandevegascasino.com/lhc_web/index.php/chat/getstatus/(click)/internal/(position)/bottom_right/(ma)/br/(check_operator_messages)/true/(top)/350/(units)/pixels/(leaveamessage)/true/(department)/22/(theme)/23?r=&l=%2F%2Fwww.grandevegascasino.com%2F
h2
4417.9310002364
4792.456000112
2008
4121
200
text/javascript
Script
https://track.grandevegascasino.com/js/container_hDwedm6V.js
http/1.1
4418.4050001204
4733.2250000909
66501
237976
200
application/javascript
Script
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
h2
4419.1220002249
4487.0119998232
40914
225312
200
application/javascript
Script
https://www.grandevegascasino.com/templates/grandevegas/fonts/CabinCondensed-Regular.woff2
h2
4423.0840001255
4453.1240002252
36446
36020
200
application/x-font-woff2
Font
https://www.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
h2
4431.865000166
4465.5659999698
74746
74320
200
application/x-font-woff2
Font
https://www.grandevegascasino.com/images/logo.png
h2
4475.7369998842
4510.2960001677
6910
6392
200
image/webp
Image
https://www.grandevegascasino.com/images/separator.png
h2
4476.0480001569
4505.4780002683
2033
1510
200
image/webp
Image
https://www.grandevegascasino.com/images/home-teaser.png
4475.7360001095
14370.349999983
0
0
-1
Image
https://www.grandevegascasino.com/modules/mod_gamesfp/helper.php
h2
4481.4949999563
4654.9889999442
508
338
411
text/html
XHR
https://secure.cdnserve.in/grandevegas/en/api/bigwinners/50
4489.757000003
14385.627000127
0
0
-1
XHR
https://track.grandevegascasino.com/matomo.js
http/1.1
4762.9040000029
4913.2590000518
49237
166397
200
application/javascript
Script
https://kbiy2d6wh8.a2btest.com/kameleoon.js
4762.0560000651
14656.253000256
0
0
-1
Script
https://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
h2
4796.1940001696
4842.7240001038
24362
88192
200
application/javascript
Script
https://track.grandevegascasino.com/matomo.php?action_name=www.grandevegascasino.com%2FGrande%20Vegas%20Online%20Casino%20-%20Get%20a%20%24300%20Bonus%20with%20%2450%20FREE&idsite=17&rec=1&r=494579&h=15&m=46&s=1&url=https%3A%2F%2Fwww.grandevegascasino.com%2F&_id=2253e606e971a1e8&_idn=1&send_image=0&_refts=0&cookie=1&res=360x640&pv_id=3YYO92&pf_net=0&pf_srv=66&pf_tfr=0&pf_dm1=24&uadata=%7B%22fullVersionList%22%3A%5B%5D%2C%22mobile%22%3Atrue%2C%22model%22%3A%22Moto%20G4%22%2C%22platform%22%3A%22Android%22%2C%22platformVersion%22%3A%226.0%22%7D
4953.3609999344
4955.909000244
0
0
-1
Ping
https://track.grandevegascasino.com/plugins/HeatmapSessionRecording/configs.php?idsite=17&trackerid=9H9IsG&url=https%3A%2F%2Fwww.grandevegascasino.com%2F
http/1.1
4961.3830000162
5116.2169999443
470
117
200
application/javascript
Script
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)
1559.341
14.426
1624.063
5.78
1662.715
44.325
4378.067
58.027
4436.109
41.977
4478.214
13.731
4493.281
14.469
4510.934
6.428
4517.475
35.641
4555.143
24.481
4580.913
6.941
4589.973
6.959
4596.942
6.429
4606.578
6.789
4623.144
5.972
4639.797
5.769
4656.387
6.876
4673.016
6.163
4706.488
5.686
4739.658
5.786
4750.958
13.951
4772.921
5.033
4823.01
5.227
4839.564
5.018
4872.949
5.139
4889.653
5.348
4906.505
7.383
4927.239
24.614
14657.691
16.62
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

Time to Interactive — 6.2 s
The time taken for the page to become fully interactive.

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Grandevegascasino.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
22667
300
Defer offscreen images — Potential savings of 31 KiB
Time to Interactive can be slowed down by resources on the page. Grandevegascasino.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.grandevegascasino.com/images/Blog/bitcoin.jpg
32168
32168
Reduce unused CSS — Potential savings of 34 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Grandevegascasino.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
22667
21855
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/41d767471fb5e12a73a715c4061788addbd8bf165fa67b1a41564e35dbe7cb9f.css
13103
13103
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://www.grandevegascasino.com/images/Blog/bitcoin.jpg
32168
8551.15
Minimize main-thread work — 2.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
682.144
Other
537.252
Script Evaluation
507.9
Rendering
225.68
Script Parsing & Compilation
91.868
Parse HTML & CSS
73.108

Metrics

First Contentful Paint — 3.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 8.3 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 4.6 s
The timing of the largest text or image that is painted.

Other

Reduce unused JavaScript — Potential savings of 181 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://track.grandevegascasino.com/js/container_hDwedm6V.js
66501
52420
https://www.grandevegascasino.com/media/com_jchoptimize/assets/gz/d78b7082dcc17b25b4dcbc0b97df27bd080c41037efddd5e831725677397c6c2.js
64540
48728
https://track.grandevegascasino.com/matomo.js
49237
32847
https://cdn.pushalert.co/integrate_5392fb8219854f0d48eb0786cdbcadf6.js
40914
27366
https://chat.grandevegascasino.com/design/defaulttheme/js/widgetv2/index.js?v120221019
24362
23902
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Grandevegascasino.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://grandevegascasino.com/
630
https://grandevegascasino.com/
480
https://www.grandevegascasino.com/
0
Serve static assets with an efficient cache policy — 20 resources found
Grandevegascasino.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://track.grandevegascasino.com/js/container_hDwedm6V.js
0
66501
https://track.grandevegascasino.com/matomo.js
0
49237
https://track.grandevegascasino.com/plugins/HeatmapSessionRecording/configs.php?idsite=17&trackerid=9H9IsG&url=https%3A%2F%2Fwww.grandevegascasino.com%2F
0
470
https://www.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
86400000
74746
https://www.grandevegascasino.com/images/homepage/teaser-bg-home.jpg
86400000
39952
https://www.grandevegascasino.com/templates/grandevegas/fonts/CabinCondensed-Regular.woff2
86400000
36446
https://www.grandevegascasino.com/images/Blog/bitcoin.jpg
86400000
32664
https://www.grandevegascasino.com/templates/grandevegas/css/bootstrap.css?18e5a32dea5eadd1a93d1898d7223326
86400000
22667
https://www.grandevegascasino.com/templates/grandevegas/css/template.min.css?18e5a32dea5eadd1a93d1898d7223326
86400000
8964
https://www.grandevegascasino.com/images/logo.png
86400000
6910
https://www.grandevegascasino.com/images/homepage/winners.png
86400000
2114
https://www.grandevegascasino.com/images/separator.png
86400000
2033
https://www.grandevegascasino.com/images/icons/05_BankingIcon.png
86400000
1071
https://www.grandevegascasino.com/images/icons/01_PromoIcon.png
86400000
930
https://www.grandevegascasino.com/images/icons/02_GamesIcon.png
86400000
919
https://www.grandevegascasino.com/images/icons/06_SupportIcon.png
86400000
912
https://www.grandevegascasino.com/images/icons/04_VIPIcon.png
86400000
795
https://www.grandevegascasino.com/images/icons/03_TournamentIcon.png
86400000
788
https://www.grandevegascasino.com/images/home.png
86400000
616
https://www.grandevegascasino.com/images/blank.png
86400000
581
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.grandevegascasino.com/templates/grandevegas/webfonts/fa-solid-900.woff2
33.700999803841
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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
https://www.grandevegascasino.com/images/logo.png
https://www.grandevegascasino.com/images/separator.png
https://www.grandevegascasino.com/images/separator.png
https://www.grandevegascasino.com/images/homepage/winners.png
https://www.grandevegascasino.com/images/home-teaser.png
First Contentful Paint (3G) — 6690 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of grandevegascasino.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 `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

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

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"]`
Grandevegascasino.com may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

Contrast

Names and labels

Links do not 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.

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
Isotope
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.
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://grandevegascasino.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.grandevegascasino.com/images/blank.png
55 x 50
1 x 1
110 x 100
https://www.grandevegascasino.com/images/homepage/winners.png
24 x 38
24 x 38
48 x 76

Audits

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_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: net::ERR_TIMED_OUT
Failed to load resource: the server responded with a status of 411 (Length Required)
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for grandevegascasino.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 grandevegascasino.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
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.
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 — 66% 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
41x24
41x24
47x24
47x24
72x24
137x24
151x24
97x24
142x24
121x24
52x24

Content Best Practices

Links do not have descriptive text — 4 links found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of grandevegascasino.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

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

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 provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 104.18.9.124
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
Safenames Ltd 45.223.58.112
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: grandevegascasino.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 3rd April, 2022
Valid To: 3rd April, 2023
Subject: CN = grandevegascasino.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: a89cdd25
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 13728517065956974885760321191792350182
Serial Number (Hex): 0A540426665EFC16E0C43F2E8D7013E6
Valid From: 3rd April, 2024
Valid To: 3rd April, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

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

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

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Apr 3 01:23:25.682 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:2E:ED:93:C2:66:92:ED:BA:48:1C:B4:0B:
46:00:57:B5:02:5A:F2:F3:E7:DD:63:7C:34:78:6F:61:
54:82:70:1B:02:20:16:51:3B:F4:3A:90:E8:92:21:92:
2E:4C:47:87:C5:BA:13:13:C5:34:90:5B:F8:F3:1E:62:
D5:C0:EC:9A:D9:C1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : Apr 3 01:23:25.679 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:88:9E:69:CB:8E:97:91:EF:29:4F:7A:
4D:0A:A3:0F:B3:E9:C5:70:28:DC:99:56:00:54:7F:FE:
1E:37:D2:A0:85:02:21:00:CA:6C:18:AC:B7:31:A4:A6:
F4:11:6C:34:09:58:CB:66:EA:D6:91:F7:64:14:89:07:
C5:41:66:53:69:5F:38:C8
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Apr 3 01:23:25.728 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:1B:52:FB:EC:49:09:87:B5:93:18:59:43:
AD:93:90:FB:EA:20:30:97:DD:0B:46:80:60:70:57:AC:
79:BD:3F:9E:02:21:00:93:FA:16:1D:BB:80:EC:B1:60:
B0:06:D4:07:C1:4D:3B:68:51:C0:A3:F9:0A:37:1B:09:
FA:31:72:55:CB:2F:9C
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.grandevegascasino.com
DNS:grandevegascasino.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 19th November, 2022
Content-Type: text/html; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, no-cache
Expires: 17th August, 2005
Server: cloudflare
Connection: keep-alive
Pragma: no-cache
Last-Modified: 19th November, 2022
Vary: Accept-Encoding
X-Powered-By: PHP/8.1.12
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM", CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
X-Content-Type-Options: nosniff
CF-Cache-Status: HIT
Age: 41109
CF-RAY: 76ccd17a2c0c8cba-EWR

Whois Lookup

Created: 1st December, 2008
Changed: 1st December, 2021
Expires: 1st December, 2023
Registrar: Safenames Ltd
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: dane.ns.cloudflare.com
lady.ns.cloudflare.com
Owner Name: Your Whois Privacy Ltd
Owner Street: Safenames House
Sunrise Parkway, Linford Wood
Owner Post Code: MK14 6LS
Owner City: Milton Keynes
Owner State: Bucks
Owner Country: GB
Owner Phone: +44.1908200022
Owner Email: domains@yourwhoisprivacy.com
Admin Name: International Domain Administrator
Admin Street: Safenames House, Sunrise Parkway
Linford Wood
Admin Post Code: MK14 6LS
Admin City: Milton Keynes
Admin State: Bucks
Admin Country: UK
Admin Phone: +44.1908200022
Admin Email: hostmaster@safenames.net
Tech Name: International Domain Tech
Tech Street: Safenames House, Sunrise Parkway
Linford Wood
Tech Post Code: MK14 6LS
Tech City: Milton Keynes
Tech State: Bucks
Tech Country: UK
Tech Phone: +44.1908200022
Tech Email: hostmaster@safenames.net
Full Whois: Domain Name: GRANDEVEGASCASINO.COM
Registry Domain ID: 1530886367_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.safenames.net
Registrar URL: http://www.safenames.net
Updated Date: 2021-12-01T03:45:30Z
Creation Date: 2008-12-01T16:58:36Z
Registrar Registration Expiration Date: 2023-12-01T16:58:36Z
Registrar: Safenames Ltd
Registrar IANA ID: 447
Registrar Abuse Contact Email: abuse@safenames.net
Registrar Abuse Contact Phone: +44.1908200022
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Your Whois Privacy Ltd
Registrant Organisation: Your Whois Privacy Ltd
Registrant Street: Safenames House
Registrant Street: Sunrise Parkway, Linford Wood
Registrant City: Milton Keynes
Registrant State/Province: Bucks
Registrant Postal Code: MK14 6LS
Registrant Country: GB
Registrant Phone: +44.1908200022
Registrant Fax: +44.1908325192
Registrant Email: domains@yourwhoisprivacy.com
Registry Admin ID: Not Available From Registry
Admin Name: International Domain Administrator
Admin Organisation: Safenames Ltd
Admin Street: Safenames House, Sunrise Parkway
Admin Street: Linford Wood
Admin City: Milton Keynes
Admin State/Province: Bucks
Admin Postal Code: MK14 6LS
Admin Country: UK
Admin Phone: +44.1908200022
Admin Fax: +44.1908325192
Admin Email: hostmaster@safenames.net
Registry Tech ID: Not Available From Registry
Tech Name: International Domain Tech
Tech Organisation: Safenames Ltd
Tech Street: Safenames House, Sunrise Parkway
Tech Street: Linford Wood
Tech City: Milton Keynes
Tech State/Province: Bucks
Tech Postal Code: MK14 6LS
Tech Country: UK
Tech Phone: +44.1908200022
Tech Fax: +44.1908325192
Tech Email: hostmaster@safenames.net
Name Server: dane.ns.cloudflare.com
Name Server: lady.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-12-01T03:45:30Z <<<

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

Safenames - Experts in Global Domain Management and Online Brand Protection

Domain Registration in over 1400 different extensions
Enterprise Domain Management since 1999
Mark Protect™ Online Brand Monitoring and Enforcement
Domain Consulting and Strategy
Domain Name Acquisition
Domain Disputes and Recovery

Visit Safenames at www.safenames.net
+1 703 574 5313 in the US/Canada
+44 1908 200022 in Europe

The Data in the Safenames Registrar WHOIS database is provided by Safenames for
information purposes only, and to assist persons in obtaining information about
or related to a domain name registration record. Safenames does not guarantee
its accuracy. Additionally, the data may not reflect updates to billing
contact information.

By submitting a WHOIS query, you agree to use this Data only for lawful purposes
and that under no circumstances will you use this Data to:

(1) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via e-mail, telephone, or facsimile; or
(2) enable high volume, automated, electronic processes that apply to Safenames
(or its computer systems). The compilation, repackaging, dissemination or
other use of this Data is expressly prohibited without the prior written
consent of Safenames. Safenames reserves the right to terminate your access to
the Safenames Registrar WHOIS database in its sole discretion, including
without limitation, for excessive querying of the WHOIS database or for failure
to otherwise abide by this policy. Safenames reserves the right to modify
these terms at any time. By submitting this query, you agree to abide by this
policy.


Nameservers

Name IP Address
dane.ns.cloudflare.com 173.245.59.97
lady.ns.cloudflare.com 173.245.58.127
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address