Porn.Gg - Info porn.gg

porn.gg receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank porn.gg is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Germany and links to network IP address 176.9.124.44. This server doesn't support HTTPS and doesn't support HTTP/2.
Loading...

About - porn.gg


Technologies used on Website

Currently Not Available

porn.gg Profile

Last update was 13 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with porn.gg in any way. Only publicly available statistics data are displayed.

How popular is porn.gg?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Loading...
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  porn.gg
Rank:
(Rank based on keywords, cost and organic traffic)
  26,675,334
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is porn.gg?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
porn.gg
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
porn.gg
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much porn.gg can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do porn.gg lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is porn.gg worth?

Website Value:
n/a

+ Where is porn.gg hosted?

Server IP:
176.9.124.44
ASN:
AS24940 
ISP:
Hetzner Online GmbH 
Server Location:

Germany, DE
 

Other sites hosted on 176.9.124.44

There are no other sites hosted on this IP

+ How fast does porn.gg load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
616 ms
7 ms
629 ms
32 ms
776 ms
46 ms
937 ms
12 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
123 ms3 ms1 ms
Avoids enormous network payloads - Total size was 17 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.porn.gg/grafik2/content-bg.gif
5 KB
http://www.porn.gg/grafik2/body-bg.gif
3 KB
http://www.porn.gg/screen2.css
3 KB
http://www.porn.gg/
2 KB
http://www.porn.gg/grafik2/logo-bg.gif
2 KB
http://www.porn.gg/grafik2/topbar_bg.gif
0 KB
http://www.porn.gg/grafik2/sidebar-bg.gif
0 KB
http://www.porn.gg/grafik2/logo-table.gif
0 KB
http://porn.gg/
0 KB
http://www.porn.gg/grafik/out_icon_adult.gif
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
71 ms
Other
22 ms
Rendering
21 ms
Parse HTML & CSS
5 ms
Script Evaluation
3 ms
Script Parsing & Compilation
1 ms
Avoids an excessive DOM size - 112 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
112
Maximum DOM Depth
8
Maximum Child Elements
16
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://porn.gg/)
0
http://www.porn.gg/
190
Keep request counts low and transfer sizes small - 11 requests • 17 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
1117 KB
Image
812 KB
Stylesheet
13 KB
Document
12 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 70 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://www.porn.gg/screen2.css
3 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://porn.gg/
0 ms295 ms0 KB0 KB301text/html
http://www.porn.gg/
296 ms591 ms2 KB6 KB200text/htmlDocument
http://www.porn.gg/screen2.css
603 ms752 ms3 KB10 KB200text/cssStylesheet
http://www.porn.gg/grafik/arrow_icon.gif
603 ms750 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik/out_icon_adult.gif
603 ms894 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik2/body-bg.gif
755 ms1042 ms3 KB3 KB200image/gifImage
http://www.porn.gg/grafik2/topbar_bg.gif
756 ms906 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik2/logo-table.gif
756 ms1042 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik2/logo-bg.gif
757 ms1054 ms2 KB1 KB200image/gifImage
http://www.porn.gg/grafik2/content-bg.gif
757 ms1044 ms5 KB5 KB200image/gifImage
http://www.porn.gg/grafik2/sidebar-bg.gif
758 ms1241 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.porn.gg/grafik2/content-bg.gif
0 ms5 KB
http://www.porn.gg/grafik2/body-bg.gif
0 ms3 KB
http://www.porn.gg/screen2.css
0 ms3 KB
http://www.porn.gg/grafik2/logo-bg.gif
0 ms2 KB
http://www.porn.gg/grafik2/topbar_bg.gif
0 ms0 KB
http://www.porn.gg/grafik2/sidebar-bg.gif
0 ms0 KB
http://www.porn.gg/grafik2/logo-table.gif
0 ms0 KB
http://www.porn.gg/grafik/out_icon_adult.gif
0 ms0 KB
http://www.porn.gg/grafik/arrow_icon.gif
0 ms0 KB
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 300 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 2790 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://porn.gg/)
0
http://www.porn.gg/
630
Keep request counts low and transfer sizes small - 9 requests • 12 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
912 KB
Image
66 KB
Stylesheet
13 KB
Document
12 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://www.porn.gg/screen2.css
3 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://porn.gg/
0 ms454 ms0 KB0 KB301text/html
http://www.porn.gg/
455 ms1236 ms2 KB6 KB200text/htmlDocument
http://www.porn.gg/screen2.css
1250 ms1543 ms3 KB10 KB200text/cssStylesheet
http://www.porn.gg/grafik/arrow_icon.gif
1251 ms1708 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik/out_icon_adult.gif
1251 ms1399 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik2/body-bg.gif
1546 ms1983 ms3 KB3 KB200image/gifImage
http://www.porn.gg/grafik2/logo-table.gif
1547 ms1839 ms0 KB0 KB200image/gifImage
http://www.porn.gg/grafik2/logo-bg.gif
1547 ms1846 ms2 KB1 KB200image/gifImage
http://www.porn.gg/grafik2/sidebar-bg.gif
1548 ms1979 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.porn.gg/grafik2/body-bg.gif
0 ms3 KB
http://www.porn.gg/screen2.css
0 ms3 KB
http://www.porn.gg/grafik2/logo-bg.gif
0 ms2 KB
http://www.porn.gg/grafik2/sidebar-bg.gif
0 ms0 KB
http://www.porn.gg/grafik2/logo-table.gif
0 ms0 KB
http://www.porn.gg/grafik/out_icon_adult.gif
0 ms0 KB
http://www.porn.gg/grafik/arrow_icon.gif
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1275 ms
9 ms
1285 ms
7 ms
1293 ms
13 ms
1581 ms
50 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
401 ms11 ms5 ms
Avoids enormous network payloads - Total size was 12 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.porn.gg/grafik2/body-bg.gif
3 KB
http://www.porn.gg/screen2.css
3 KB
http://www.porn.gg/
2 KB
http://www.porn.gg/grafik2/logo-bg.gif
2 KB
http://www.porn.gg/grafik2/sidebar-bg.gif
0 KB
http://www.porn.gg/grafik2/logo-table.gif
0 KB
http://porn.gg/
0 KB
http://www.porn.gg/grafik/out_icon_adult.gif
0 KB
http://www.porn.gg/grafik/arrow_icon.gif
0 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
236 ms
Other
86 ms
Rendering
33 ms
Parse HTML & CSS
31 ms
Script Evaluation
11 ms
Script Parsing & Compilation
5 ms
Avoids an excessive DOM size - 112 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
112
Maximum DOM Depth
8
Maximum Child Elements
16
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 780 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/dating.html">Dating</a> and 2 others are close to other tap targets .
The tap target <a href="/erotik.html">Erotik</a> and 1 others are close to other tap targets .
The tap target <a href="/erotikchat.html">Erotikchat</a> and 7 others are close to other tap targets .
The tap target <a href="/live***.html">Live***</a> is close to 1 other tap targets .
The tap target <a href="/***o.html">***o</a> is close to 1 other tap targets .
The tap target <a href="/***ofilme.html">***ofilme</a> is close to 2 other tap targets .
The tap target <a href="/***os.html">***os</a> is close to 1 other tap targets .
The tap target <a href="/strapshemd-viola.html">Strapshemd Viola</a> and 1 others are close to other tap targets .

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

http://www.***.gg/screen2.css

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.***.gg/grafik/arrow_icon.gif (expiration not specified)
http://www.***.gg/grafik/out_icon_***.gif (expiration not specified)
http://www.***.gg/grafik2/body-bg.gif (expiration not specified)
http://www.***.gg/grafik2/logo-bg.gif (expiration not specified)
http://www.***.gg/grafik2/logo-table.gif (expiration not specified)
http://www.***.gg/grafik2/sidebar-bg.gif (expiration not specified)
http://www.***.gg/screen2.css (expiration not specified)

Reduce server response time

In our test, your server responded in 0.42 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 331B (14% reduction).

Minifying http://www.***.gg/screen2.css could save 331B (14% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does porn.gg use compression?

porn.gg does not use compression.
Original size: n/a
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

porn.gg does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

porn.gg does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Currently Not Available

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.gg...
Domain:
***.gg

Domain Status:
Active


Registrant:
KV GmbH

Registrar:
InterNetX GmbH (http://www.internetx.com)

Relevant dates:
Registered on 30th April 2008
Registry fee due on 30th April each year

Registration status:
Registered until cancelled

Name servers:
ns1.birawu.com
ns2.birawu.com


WHOIS lookup made on Sat, 9 Nov 2019 at 0:15:39 UTC

This WHOIS information is provided for free by CIDR, operator of
the backend registry for domain names ending in GG, JE, and AS.

Copyright (c) and database right Island Networks 1996 - 2019.

You may not access this WHOIS server or use any data from it except
as permitted by our Terms and Conditions which are published
at http://www.channelisles.net/legal/whoisterms

They include restrictions and prohibitions on

- using or re-using the data for advertising;
- using or re-using the service for commercial purposes without a licence;
- repackaging, recompilation, redistribution or reuse;
- obscuring, removing or hiding any or all of this notice;
- exceeding query rate or volume limits.

The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.
Last update was 13 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with porn.gg in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

task.exalo.pl
7 secs
speedoutboard.com
18 secs
ecosoli.com.br
22 secs
taojinbi.taobao.com
1 min
ecoplus.ind.br
1 min
primecc.su
2 mins
econbank.com.br
2 mins
rukomarine.com
3 mins
ecoagro.agr.br
3 mins
tangysoft.net
4 mins

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
porn.gg widget