ggg.com

ggg.com may not be SSL secured

Free website and domain report on ggg.com

Last Updated: 21st March, 2023 Update Now
Overview

Snoop Summary for ggg.com

This is a free and comprehensive report about ggg.com. Ggg.com is hosted in Canada on a server with an IP address of 104.247.81.54, where CAD is the local currency and the local language is English. Ggg.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If ggg.com was to be sold it would possibly be worth $1,022 USD (based on the daily revenue potential of the website over a 24 month period). Ggg.com is somewhat popular with an estimated 486 daily unique visitors. This report was last updated 21st March, 2023.

About ggg.com

Site Preview: ggg.com ggg.com
Title: ggg.com
Description:
Keywords and Tags: alcohol
Related Terms: betty ggg, ggg, ggg sperm
Fav Icon:
Age: Over 29 years old
Domain Created: 22nd April, 1995
Domain Updated: 17th December, 2019
Domain Expires: 23rd April, 2021
Review

Snoop Score

1/5

Valuation

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

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,335,217
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: 486
Monthly Visitors: 14,806
Yearly Visitors: 177,556
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $42 USD
Yearly Revenue: $506 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: ggg.com 7
Domain Name: ggg 3
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 74
Performance 94
Accessibility 86
Best Practices 79
SEO 80
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ggg.com/
Updated: 3rd November, 2020

2.95 seconds
First Contentful Paint (FCP)
13%
63%
24%

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

Simulate loading on desktop
94

Performance

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

Metrics

Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.3 s
The time taken for the page to become fully interactive.
Total Blocking Time — 130 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.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive ggg.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ggg.com/
0
245.87199999951
5523
10959
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
262.21800000349
279.56799999811
63181
179307
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
262.54599999811
292.54799999762
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
262.75100000203
280.40599999076
1055
1417
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins:300
262.92100000137
280.71199999249
1425
1176
200
text/css
Stylesheet
http://c.parkingcrew.net/scripts/sale_form.js
263.34099999804
649.69199999177
1005
761
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
263.83300000452
284.8149999918
7454
7000
200
application/javascript
Script
http://ggg.com/track.php?domain=ggg.com&toggle=browserjs&uid=MTYwNDQzNDkwNS45NTY3OjIxNDBiMzAxNDNiMjNhNmQ5MTYxMTIzYmYzYjI3MDNlZDZiZDQyNTI4MTlkM2JmNWYwMWZkNzViYjA3YjhlZWI6NWZhMWJiZDllOTk0Mw%3D%3D
661.70799999963
809.61100000422
300
0
200
text/html
XHR
http://ggg.com/ls.php
813.34399999469
867.07300000126
300
0
201
text/javascript
XHR
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
825.88200000464
843.57699999237
15986
15544
200
image/png
Image
https://fonts.gstatic.com/s/poppins/v13/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
828.37400000426
833.39200000046
8443
7848
200
font/woff2
Font
https://www.google.com/afs/ads/i/iframe.html
852.00699999405
856.72999999952
1551
1243
200
text/html
Document
https://www.google.com/dp/ads?max_radlink_len=40&r=m&cpp=0&client=dp-teaminternet09_3ph&channel=000002%2Cbucket011&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2750267643137968&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300441%2C17300443&format=r5%7Cs&num=0&output=afd_ads&domain_name=ggg.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1604434906614&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=864&frm=0&uio=ff2sa16fa2sl1sr1-st24sa14lt34-&cont=tc&csize=w522h0&inames=master-1&jsv=13811&rurl=http%3A%2F%2Fggg.com%2F
861.88199999742
951.73400000203
8113
10324
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
963.30699999817
980.81500000262
64766
179307
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Poppins
1017.5909999962
1033.8699999993
1325
1176
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Poppins
1042.002999995
1058.8949999947
1486
1176
200
text/css
Stylesheet
http://ggg.com/track.php?domain=ggg.com&caf=1&toggle=answercheck&answer=yes&uid=MTYwNDQzNDkwNS45NTY3OjIxNDBiMzAxNDNiMjNhNmQ5MTYxMTIzYmYzYjI3MDNlZDZiZDQyNTI4MTlkM2JmNWYwMWZkNzViYjA3YjhlZWI6NWZhMWJiZDllOTk0Mw%3D%3D
1052.7509999956
1150.5139999936
302
0
200
text/html
XHR
https://www.gstatic.com/domainads/images/chevron-white.png
1155.5970000045
1159.2470000032
726
189
200
image/png
Image
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
1167.0920000033
1170.7820000011
6668
14063
200
text/javascript
Script
https://fonts.gstatic.com/s/poppins/v13/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
1170.603999999
1173.5170000029
8495
7900
200
font/woff2
Font
https://fonts.gstatic.com/s/poppins/v13/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
1177.3410000023
1180.1649999979
8495
7900
200
font/woff2
Font
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
1343.1039999996
1343.234999993
6668
14063
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=qcg28m8l6qf1&aqid=2ruhX5ayKsz-j-8P99Sh6AI&pbt=bs&adbx=414&adby=119&adbh=364&adbw=522&adbn=master-1&eawp=partner-dp-teaminternet09_3ph&errv=13811087015461537366&csadii=39&csadr=327&pblt=1&lle=0&llm=0&ifv=1
2692.888000005
2720.6829999923
520
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=l9g3y1dvmarm&pbt=bs&adbx=415&adby=500&adbh=20&adbw=521&adbn=slave-1-1&eawp=partner-dp-teaminternet09_3ph&errv=13811087015461537366&csadii=31&csadr=337&pblt=1&lle=0&llm=0&ifv=1
2700.5130000034
2729.7229999967
520
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
277.943
9.313
320.552
9.425
679.89
212.203
900.745
8.299
914.886
7.171
983.627
5.941
1021.57
53.183
1075.489
104.376
1179.877
11.843
1195.374
6.141
1215.825
14.171
1230.112
133.74
1364.255
6.973
1373.685
121.806
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Ggg.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ggg.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ggg.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ggg.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ggg.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ggg.com/
246.868
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Ggg.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ggg.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 210 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
64766
http://www.google.com/adsense/domains/caf.js
63181
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
15986
https://fonts.gstatic.com/s/poppins/v13/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
8495
https://fonts.gstatic.com/s/poppins/v13/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
8495
https://fonts.gstatic.com/s/poppins/v13/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
8443
https://www.google.com/dp/ads?max_radlink_len=40&r=m&cpp=0&client=dp-teaminternet09_3ph&channel=000002%2Cbucket011&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2750267643137968&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300441%2C17300443&format=r5%7Cs&num=0&output=afd_ads&domain_name=ggg.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1604434906614&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=864&frm=0&uio=ff2sa16fa2sl1sr1-st24sa14lt34-&cont=tc&csize=w522h0&inames=master-1&jsv=13811&rurl=http%3A%2F%2Fggg.com%2F
8113
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7454
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
6668
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
6668
Uses efficient cache policy on static assets — 5 resources found
Ggg.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
0
15986
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7454
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
0
1055
http://c.parkingcrew.net/scripts/sale_form.js
0
1005
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
Avoids an excessive DOM size — 39 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
39
Maximum DOM Depth
8
Maximum Child Elements
14
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ggg.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.google.com/adsense/domains/caf.js
326.634
292.594
8.233
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
155.557
154.988
0.569
http://www.google.com/adsense/domains/caf.js
138.64
111.544
3.87
http://ggg.com/
64.843
34.486
3.066
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
607.694
Other
68.594
Style & Layout
48.342
Script Parsing & Compilation
20.22
Parse HTML & CSS
11.856
Rendering
10.366
Garbage Collection
4.945
Keep request counts low and transfer sizes small — 24 requests • 210 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
24
215134
Script
6
149742
Font
3
25433
Image
4
17752
Document
3
15187
Stylesheet
5
6118
Other
3
902
Media
0
0
Third-party
20
208709
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
div
0.0026618754925138
0.00082277237449651
0.00018465647181462
0.00017267875472394
0.00017267875472394
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 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.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
1050
134
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
1187
122
http://c.parkingcrew.net/scripts/sale_form.js
540
106
http://www.google.com/adsense/domains/caf.js
646
104
https://www.google.com/adsense/domains/caf.js
990
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 620 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ggg.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www.google.com/adsense/domains/caf.js
63181
350
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
190
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
1055
190
https://fonts.googleapis.com/css?family=Poppins:300
1425
230
Remove unused JavaScript — Potential savings of 76 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
63181
41484
https://www.google.com/adsense/domains/caf.js
64766
36567

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/poppins/v13/pxiByp8kv8JHgFVrLDz8Z1xlFd2JQEk.woff2
5.0179999961983
https://fonts.gstatic.com/s/poppins/v13/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.9130000039004
https://fonts.gstatic.com/s/poppins/v13/pxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
2.8239999955986
Reduce the impact of third-party code — Third-party code blocked the main thread for 280 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
151987
174.371
26327
102.204
29669
0
726
0
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 203
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ggg.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.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[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-*]` 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

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

Contrast

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 10 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ggg.com/
http://www.google.com/adsense/domains/caf.js
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
http://c.parkingcrew.net/scripts/sale_form.js
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http://ggg.com/track.php?domain=ggg.com&toggle=browserjs&uid=MTYwNDQzNDkwNS45NTY3OjIxNDBiMzAxNDNiMjNhNmQ5MTYxMTIzYmYzYjI3MDNlZDZiZDQyNTI4MTlkM2JmNWYwMWZkNzViYjA3YjhlZWI6NWZhMWJiZDllOTk0Mw%3D%3D
http://ggg.com/ls.php
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
http://ggg.com/track.php?domain=ggg.com&caf=1&toggle=answercheck&answer=yes&uid=MTYwNDQzNDkwNS45NTY3OjIxNDBiMzAxNDNiMjNhNmQ5MTYxMTIzYmYzYjI3MDNlZDZiZDQyNTI4MTlkM2JmNWYwMWZkNzViYjA3YjhlZWI6NWZhMWJiZDllOTk0Mw%3D%3D
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning URL
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ggg.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 ggg.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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
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

Document does not have 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.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

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

Progressive Web App

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

Fast and reliable

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

PWA Optimized

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

Fast and reliable

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

Installable

Does not use HTTPS — 10 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ggg.com/
http://www.google.com/adsense/domains/caf.js
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
http://c.parkingcrew.net/scripts/sale_form.js
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http://ggg.com/track.php?domain=ggg.com&toggle=browserjs&uid=MTYwNDQzNDkwNS45NTY3OjIxNDBiMzAxNDNiMjNhNmQ5MTYxMTIzYmYzYjI3MDNlZDZiZDQyNTI4MTlkM2JmNWYwMWZkNzViYjA3YjhlZWI6NWZhMWJiZDllOTk0Mw%3D%3D
http://ggg.com/ls.php
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
http://ggg.com/track.php?domain=ggg.com&caf=1&toggle=answercheck&answer=yes&uid=MTYwNDQzNDkwNS45NTY3OjIxNDBiMzAxNDNiMjNhNmQ5MTYxMTIzYmYzYjI3MDNlZDZiZDQyNTI4MTlkM2JmNWYwMWZkNzViYjA3YjhlZWI6NWZhMWJiZDllOTk0Mw%3D%3D
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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) 60
Performance 58
Accessibility 53
Best Practices 79
SEO 75
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://ggg.com/
Updated: 3rd November, 2020

3.95 seconds
First Contentful Paint (FCP)
9%
49%
42%

0.03 seconds
First Input Delay (FID)
86%
6%
8%

Simulate loading on mobile
58

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Ggg.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Ggg.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Ggg.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Ggg.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Ggg.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 80 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ggg.com/
78.088
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Ggg.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Ggg.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 177 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
64502
http://www.google.com/adsense/domains/caf.js
63181
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
11011
https://www.google.com/dp/ads?max_radlink_len=40&r=m&cpp=0&client=dp-mobile-teaminternet02_3ph&channel=000002%2Cbucket009&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2750267643137968&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300441%2C17300443&format=r5%7Cs&num=0&output=afd_ads&domain_name=ggg.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1604434917056&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=377&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1st16sa13lt50-ff1fa1&cont=tc&csize=w316h0&inames=master-1&jsv=13811&rurl=http%3A%2F%2Fggg.com%2F
8087
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7454
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
6672
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
6672
http://ggg.com/
5599
https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif
1617
https://www.google.com/afs/ads/i/iframe.html
1580
Uses efficient cache policy on static assets — 6 resources found
Ggg.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
0
11011
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7454
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
0
1164
http://c.parkingcrew.net/scripts/sale_form.js
0
1005
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
0
641
https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif
82800000
1617
Avoids an excessive DOM size — 37 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
37
Maximum DOM Depth
5
Maximum Child Elements
15
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Ggg.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.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 18 requests • 177 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
18
181127
Script
6
149486
Document
3
15266
Image
4
13668
Stylesheet
2
1805
Other
3
902
Media
0
0
Font
0
0
Third-party
14
174626
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.14254894251815
0.087777321300287
0.046524656426997
0.035949451711398
0.0053924177567097
Avoid long main-thread tasks — 6 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.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
4147
580
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
3660
487
http://www.google.com/adsense/domains/caf.js
2128
233
https://www.google.com/adsense/domains/caf.js
3300
232
http://c.parkingcrew.net/scripts/sale_form.js
1912
216
http://www.google.com/adsense/domains/caf.js
1860
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://ggg.com/
0
77.091000042856
5599
11048
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
95.204000361264
160.48600059003
63181
179307
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
95.487999729812
112.81100008637
641
220
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
95.793000422418
124.84399974346
1164
1728
200
text/css
Stylesheet
http://c.parkingcrew.net/scripts/sale_form.js
96.312000416219
215.79500008374
1005
761
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
96.81100025773
113.39200008661
7454
7000
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
188.331999816
205.27700055391
11011
10569
200
image/png
Image
http://ggg.com/track.php?domain=ggg.com&toggle=browserjs&uid=MTYwNDQzNDkxNi44MDYzOmRmN2ZmOTM1OTE3YmNiMDhmYWNmMWY3YjVkNmY5MmZkNDU3ZmU5NGNjZjg3MjY0MjEyOWI2YTVmODk2MGI5NDI6NWZhMWJiZTRjNGQ3Yw%3D%3D
224.66900013387
278.58099993318
300
0
200
text/html
XHR
http://ggg.com/ls.php
282.00700040907
336.32500004023
300
0
201
text/javascript
XHR
https://www.google.com/afs/ads/i/iframe.html
311.41700036824
317.48300045729
1580
1243
200
text/html
Document
https://www.google.com/dp/ads?max_radlink_len=40&r=m&cpp=0&client=dp-mobile-teaminternet02_3ph&channel=000002%2Cbucket009&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2750267643137968&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300441%2C17300443&format=r5%7Cs&num=0&output=afd_ads&domain_name=ggg.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1604434917056&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=377&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1st16sa13lt50-ff1fa1&cont=tc&csize=w316h0&inames=master-1&jsv=13811&rurl=http%3A%2F%2Fggg.com%2F
320.91900054365
422.09800053388
8087
10288
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
435.99299993366
454.23500053585
64502
179316
200
text/javascript
Script
https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif
524.71600007266
534.20799970627
1617
1095
200
image/gif
Image
http://ggg.com/track.php?domain=ggg.com&caf=1&toggle=answercheck&answer=yes&uid=MTYwNDQzNDkxNi44MDYzOmRmN2ZmOTM1OTE3YmNiMDhmYWNmMWY3YjVkNmY5MmZkNDU3ZmU5NGNjZjg3MjY0MjEyOWI2YTVmODk2MGI5NDI6NWZhMWJiZTRjNGQ3Yw%3D%3D
529.10699974746
583.45399983227
302
0
200
text/html
XHR
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
593.70400011539
597.48299978673
6672
14063
200
text/javascript
Script
https://www.google.com/js/bg/sYBZi8RubymXUPMccEHraxS349Tofqq0Y87esqoxnno.js
622.67899978906
628.05199995637
6672
14063
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_3ph&output=uds_ads_only&zx=42brhng3fpl1&aqid=5buhX_ikCPrsj-8PlMemwAk&pbt=bs&adbx=10&adby=66.46875&adbh=420&adbw=340&adbn=master-1&eawp=partner-dp-mobile-teaminternet02_3ph&errv=13811087015461537366&csadii=30&csadr=300&pblt=1&lle=0&llm=0&ifv=1
2118.3160003275
2145.0249999762
520
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_3ph&output=uds_ads_only&zx=zcfref8k9h9l&pbt=bs&adbx=10&adby=511.46875&adbh=18&adbw=340&adbn=slave-1-1&eawp=partner-dp-mobile-teaminternet02_3ph&errv=13811087015461537366&csadii=20&csadr=312&pblt=1&lle=0&llm=0&ifv=1
2121.1080001667
2151.9160000607
520
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
116.487
10.495
209.768
13.018
222.87
7.901
253.699
108.169
365.65
8.484
376.83
5.078
462.143
7.628
503.4
58.089
562.526
58.193
620.737
6.164
633.331
14.748
659.998
121.736
784.779
145.075
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.5 s
The timing of the largest text or image that is painted.
Time to Interactive — 4.7 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.6 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.3 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused JavaScript — Potential savings of 76 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
63181
41484
https://www.google.com/adsense/domains/caf.js
64502
36666

Diagnostics

Reduce JavaScript execution time — 2.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.google.com/adsense/domains/caf.js
1333.628
1224.164
37.78
http://www.google.com/adsense/domains/caf.js
346.252
276.796
17.808
http://ggg.com/
276.412
156.024
14.292
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
238.296
236.34
1.956
Unattributable
126.556
12.012
0.592
https://www.google.com/afs/ads/i/iframe.html
51.644
10.336
4.5
Minimize main-thread work — 2.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1952.768
Other
232.188
Style & Layout
112.74
Script Parsing & Compilation
90.924
Parse HTML & CSS
41.888
Garbage Collection
30.4
Rendering
25.864

Metrics

Total Blocking Time — 1,030 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.318
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 580 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 240 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive ggg.com as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 6581 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,970 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Ggg.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://www.google.com/adsense/domains/caf.js
63181
1230
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
641
630
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
1164
630

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 1,270 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
151734
1101.688
21275
169.892
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 136
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 203
53

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of ggg.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.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[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-*]` 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

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

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

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

Contrast

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

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

Best practices

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

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

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

Audits

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

Audits

Avoids `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.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 10 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ggg.com/
http://www.google.com/adsense/domains/caf.js
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
http://c.parkingcrew.net/scripts/sale_form.js
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
http://ggg.com/track.php?domain=ggg.com&toggle=browserjs&uid=MTYwNDQzNDkxNi44MDYzOmRmN2ZmOTM1OTE3YmNiMDhmYWNmMWY3YjVkNmY5MmZkNDU3ZmU5NGNjZjg3MjY0MjEyOWI2YTVmODk2MGI5NDI6NWZhMWJiZTRjNGQ3Yw%3D%3D
http://ggg.com/ls.php
http://ggg.com/track.php?domain=ggg.com&caf=1&toggle=answercheck&answer=yes&uid=MTYwNDQzNDkxNi44MDYzOmRmN2ZmOTM1OTE3YmNiMDhmYWNmMWY3YjVkNmY5MmZkNDU3ZmU5NGNjZjg3MjY0MjEyOWI2YTVmODk2MGI5NDI6NWZhMWJiZTRjNGQ3Yw%3D%3D
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning URL
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for ggg.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 ggg.com on mobile screens.
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
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

Document does not have 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.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Mobile Friendly

Document doesn't use legible font sizes — 9.76% 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
#sub
90.24%
10px
9.76%
≥ 12px

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

Progressive Web App

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

Fast and reliable

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

PWA Optimized

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

Fast and reliable

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

Installable

Does not use HTTPS — 10 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://ggg.com/
http://www.google.com/adsense/domains/caf.js
http://d1lxhc4jvstzrp.cloudfront.net/themes/saledefaultmobile.css
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
http://c.parkingcrew.net/scripts/sale_form.js
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
http://ggg.com/track.php?domain=ggg.com&toggle=browserjs&uid=MTYwNDQzNDkxNi44MDYzOmRmN2ZmOTM1OTE3YmNiMDhmYWNmMWY3YjVkNmY5MmZkNDU3ZmU5NGNjZjg3MjY0MjEyOWI2YTVmODk2MGI5NDI6NWZhMWJiZTRjNGQ3Yw%3D%3D
http://ggg.com/ls.php
http://ggg.com/track.php?domain=ggg.com&caf=1&toggle=answercheck&answer=yes&uid=MTYwNDQzNDkxNi44MDYzOmRmN2ZmOTM1OTE3YmNiMDhmYWNmMWY3YjVkNmY5MmZkNDU3ZmU5NGNjZjg3MjY0MjEyOWI2YTVmODk2MGI5NDI6NWZhMWJiZTRjNGQ3Yw%3D%3D
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.247.81.54
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
Team Internet AG
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
Key-Systems GmbH 104.22.34.174
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 4.3/5
WOT Trustworthiness: 86/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
ggg.com. 104.247.81.54 IN 599

NS Records

Host Nameserver Class TTL
ggg.com. ns1.parkingcrew.net. IN 3599
ggg.com. ns2.parkingcrew.net. IN 3599

MX Records

Priority Host Server Class TTL
5 ggg.com. mail.h-email.net. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
ggg.com. ns1.parkingcrew.net. hostmaster.ggg.com. 10799

TXT Records

Host Value Class TTL
ggg.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 3rd November, 2020
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Check: 3c12dc4d54f8e22d666785b733b0052100c53444
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_Y0RMr9gifSKklJ1xbhTWs63QgaDQuMh1/04JdLiiMuoJDSWovzgJxhIu/NophXLd8yTv1oPnOJfgqdbsBIfB9w==

Whois Lookup

Created: 22nd April, 1995
Changed: 17th December, 2019
Expires: 23rd April, 2021
Registrar: Key-Systems GmbH
Status: clientTransferProhibited
Nameservers: ns1.parkingcrew.net
ns2.parkingcrew.net
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner Country: NL
Owner Phone: REDACTED FOR PRIVACY
Owner Email: info@domain-contact.org
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: info@domain-contact.org
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: info@domain-contact.org
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
REDACTED FOR PRIVACY
Billing Post Code: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Email: info@domain-contact.org
Full Whois: Domain Name: ggg.com
Registry Domain ID: 1096364_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.key-systems.net
Updated Date: 2019-12-17T14:16:03Z
Creation Date: 1995-04-22T04:00:00Z
Registrar Registration Expiration Date: 2021-04-23T04:00:00Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: abusereport@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: NL
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: info@domain-contact.org
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: info@domain-contact.org
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: info@domain-contact.org
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Phone Ext: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Fax Ext: REDACTED FOR PRIVACY
Billing Email: info@domain-contact.org
Name Server: ns1.parkingcrew.net
Name Server: ns2.parkingcrew.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-11-03T20:21:43Z <<<

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

To contact the registered registrant please proceed to:
https://www.domain-contact.org

Please register your domains at; http://www.key-systems.net
This data is provided by
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data
only for lawful purposes and that, under no circumstances, you will
use this data to
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail
(spam) or
2) enable high volume, automated, electronic processes that apply
to this WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
ns1.parkingcrew.net 13.248.158.159
ns2.parkingcrew.net 76.223.21.9
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$1,416,507 USD 4/5
$823 USD 1/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$1,031 USD 1/5
0/5
0/5
$275 USD

Sites hosted on the same IP address

Domain Valuation Snoop Score
$2,656 USD 2/5
0/5
$601 USD 1/5