pangea2.Group - Info pangea2.group

pangea2.group receives about 797 unique visitors and 5,662 (7.10 per visitor) page views per day which should earn about $62.99/day from advertising revenue. Estimated site value is $26,498.58. According to Alexa Traffic Rank pangea2.group is ranked number 665,299 in the world and 4.7E-5% of global Internet users visit it. Site is hosted in Toronto, Ontario, M8W, Canada and links to network IP address 64.34.196.230. This server supports HTTPS and doesn't support HTTP/2.

About - pangea2.group


Technologies used on Website

Web Servers
Apache
Font Scripts
Google Font API
Hosting Panels
Plesk

pangea2.group Profile

Title: Pangea2.Group Big Email Advertising
Description: Safelist Advertising at its best
Keywords: safelist,advertising,pangea,money,email,ads
Last update was 302 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is pangea2.group?

797 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
797
Monthly Unique Visitors:
19,128
Pages per Visit:
7.10
Daily Pageviews:
5,662
Alexa Rank:
665,299 visit alexa
Alexa Reach:
4.7E-5%   (of global internet users)
Avg. visit duration:
00:04
Bounce rate:
50.00%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
100.00%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
United States 88.6%97.0%120333

Where do visitors go on this site?

Reach%Pageviews%PerUser
pangea2.group
100.00%100.00%11

Competitive Data

SEMrush
Domain:
  pangea2.group
Rank:
(Rank based on keywords, cost and organic traffic)
  5,255,536
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
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 pangea2.group?

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:
pangea2.group
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:
pangea2.group
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 pangea2.group can earn?

Daily Revenue:
$62.99
Monthly Revenue:
$1,889.70
Yearly Revenue:
$22,991.35
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 5,492$62.99

How much money do pangea2.group lose due to Adblock?

Daily Revenue Loss:
$11.34
Monthly Revenue Loss:
$340.17
Yearly Revenue Loss:
$4,138.76
Daily Pageviews Blocked:
989
Monthly Pageviews Blocked:
29,658
Yearly Pageviews Blocked:
360,834
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 989$11.34

How much is pangea2.group worth?

Website Value:
$26,498.58

+ Where is pangea2.group hosted?

Server IP:
64.34.196.230
ASN:
AS13768 
ISP:
Cogeco Peer 1 
Server Location:
Toronto
Ontario, ON
M8W
Canada, CA
 

Other sites hosted on 64.34.196.230

+ How fast does pangea2.group load?

Average Load Time:
(425 ms) 97 % 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

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.
Max Potential First Input Delay 50 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.
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 0.4 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.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 21 requests • 216 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
21216 KB
Script
592 KB
Font
160 KB
Image
841 KB
Document
211 KB
Stylesheet
411 KB
Other
11 KB
Media
00 KB
Third-party
15170 KB
Eliminate render-blocking resources - Potential savings of 0 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://pangea2.group/translate/style.css
2 KB70
Enable text compression - Potential savings of 7 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://pangea2.group/
10 KB7 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pangea2.group/
0 ms22 ms10 KB10 KB200text/htmlDocument
https://fonts.googleapis.com/icon?family=Material+Icons
33 ms56 ms1 KB1 KB200text/cssStylesheet
http://pangea2.group/translate/style.css
33 ms72 ms2 KB2 KB200text/cssStylesheet
http://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit
33 ms73 ms1 KB2 KB200text/javascriptScript
http://pangea2.group/merged.png
34 ms73 ms6 KB6 KB200image/pngImage
http://pangea2.group/pang3.png
34 ms73 ms17 KB16 KB200image/pngImage
http://pangea2.group/general.png
36 ms76 ms11 KB11 KB200image/pngImage
http://trafficadbar.com/bar/show.js
36 ms74 ms1 KB0 KB200application/javascriptScript
https://fonts.googleapis.com/icon?family=Material+Icons
37 ms77 ms1 KB0 KB200text/cssOther
https://translate.googleapis.com/translate_static/css/translateelement.css
92 ms119 ms4 KB18 KB200text/cssStylesheet
https://translate.googleapis.com/translate_static/js/element/main.js
93 ms119 ms2 KB3 KB200text/javascriptScript
http://trafficadbar.com/bar/page.php?a=webstars&b=490&c=90&e=%23ffffff&f=%23AC0101&g=%23f8f8f8&h=%23000000&i=%237c8e06&d=http%3A//pangea2.group/
120 ms166 ms1 KB2 KB200text/htmlDocument
https://translate.googleapis.com/element/TE_20190506_00/e/js/element/element_main.js
128 ms167 ms87 KB239 KB200text/javascriptScript
http://trafficadbar.com/images/home_logo_88.png
174 ms194 ms2 KB2 KB200image/pngImage
https://translate.googleapis.com/translate_a/l?client=te&alpha=true&hl=en&cb=_callbacks____0jwopuks0
216 ms246 ms2 KB3 KB200application/javascriptScript
https://www.gstatic.com/images/branding/product/2x/translate_24dp.png
226 ms246 ms2 KB2 KB200image/pngImage
https://translate.googleapis.com/translate_static/css/translateelement.css
229 ms229 ms4 KB18 KB200text/cssStylesheet
https://www.gstatic.com/images/branding/product/1x/translate_24dp.png
230 ms246 ms1 KB1 KB200image/pngImage
https://www.google.com/images/cleardot.gif
230 ms247 ms0 KB0 KB200image/gifImage
http://pangea2.group/translate/32.png
261 ms299 ms0 KB0 KB200image/pngImage
https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2
262 ms300 ms60 KB59 KB200font/woff2Font
Serve static assets with an efficient cache policy - 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://pangea2.group/pang3.png
0 ms17 KB
http://pangea2.group/general.png
0 ms11 KB
http://pangea2.group/merged.png
0 ms6 KB
http://pangea2.group/translate/style.css
0 ms2 KB
http://pangea2.group/translate/32.png
0 ms0 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
3600000 ms4 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
3600000 ms4 KB
https://translate.googleapis.com/translate_static/js/element/main.js
3600000 ms2 KB
http://trafficadbar.com/images/home_logo_88.png
5184000000 ms2 KB
http://trafficadbar.com/bar/show.js
5184000000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
41 ms
6 ms
94 ms
13 ms
108 ms
6 ms
114 ms
16 ms
136 ms
6 ms
197 ms
6 ms
203 ms
45 ms
265 ms
13 ms
277 ms
9 ms
317 ms
15 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2
38 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
173 ms4 ms1 ms
Remove unused CSS - Potential savings of 0 KB
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.

URL
SizePotential Savings
https://fonts.googleapis.com/icon?family=Material+Icons
0 KB0 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
4 KB4 KB
Avoids enormous network payloads - Total size was 216 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://translate.googleapis.com/element/TE_20190506_00/e/js/element/element_main.js
87 KB
https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2
60 KB
http://pangea2.group/pang3.png
17 KB
http://pangea2.group/general.png
11 KB
http://pangea2.group/
10 KB
http://pangea2.group/merged.png
6 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
4 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
4 KB
http://trafficadbar.com/images/home_logo_88.png
2 KB
https://www.gstatic.com/images/branding/product/2x/translate_24dp.png
2 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
74 ms
Other
61 ms
Script Evaluation
47 ms
Rendering
32 ms
Parse HTML & CSS
14 ms
Script Parsing & Compilation
10 ms
Garbage Collection
0 ms
Serve images in next-gen formats - Potential savings of 11 KB
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.

URL
SizePotential Savings
http://pangea2.group/pang3.png
16 KB11 KB
Avoids an excessive DOM size - 249 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
249
Maximum DOM Depth
26
Maximum Child Elements
24
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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 20 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.

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.

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.

Minimize Critical Requests Depth - 5 chains 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.


Page Speed (Google PageSpeed Insights) - Mobile

97
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 180 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 3.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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.
First Contentful Paint (3G) 2760 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.0 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.
First Meaningful Paint 1.4 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.

Eliminate render-blocking resources - Potential savings of 0 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://pangea2.group/translate/style.css
2 KB180
Enable text compression - Potential savings of 7 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://pangea2.group/
10 KB7 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://pangea2.group/
0 ms54 ms10 KB10 KB200text/htmlDocument
https://fonts.googleapis.com/icon?family=Material+Icons
66 ms88 ms1 KB1 KB200text/cssStylesheet
http://pangea2.group/translate/style.css
66 ms138 ms2 KB2 KB200text/cssStylesheet
http://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit
66 ms138 ms1 KB2 KB200text/javascriptScript
http://pangea2.group/merged.png
66 ms139 ms6 KB6 KB200image/pngImage
http://pangea2.group/pang3.png
67 ms139 ms17 KB16 KB200image/pngImage
http://pangea2.group/general.png
68 ms148 ms11 KB11 KB200image/pngImage
http://trafficadbar.com/bar/show.js
68 ms143 ms1 KB0 KB200application/javascriptScript
https://fonts.googleapis.com/icon?family=Material+Icons
68 ms148 ms1 KB0 KB200text/cssOther
https://translate.googleapis.com/translate_static/css/translateelement.css
150 ms180 ms4 KB18 KB200text/cssStylesheet
https://translate.googleapis.com/translate_static/js/element/main.js
150 ms180 ms2 KB3 KB200text/javascriptScript
http://trafficadbar.com/bar/page.php?a=webstars&b=490&c=90&e=%23ffffff&f=%23AC0101&g=%23f8f8f8&h=%23000000&i=%237c8e06&d=http%3A//pangea2.group/
182 ms270 ms1 KB2 KB200text/htmlDocument
https://translate.googleapis.com/element/TE_20190506_00/e/js/element/element_main.js
187 ms271 ms87 KB239 KB200text/javascriptScript
http://trafficadbar.com/images/home_logo_88.png
280 ms299 ms2 KB2 KB200image/pngImage
https://translate.googleapis.com/translate_a/l?client=te&alpha=true&hl=en&cb=_callbacks____0jwopuhak
318 ms354 ms2 KB3 KB200application/javascriptScript
https://www.gstatic.com/images/branding/product/2x/translate_24dp.png
329 ms354 ms2 KB2 KB200image/pngImage
https://translate.googleapis.com/translate_static/css/translateelement.css
332 ms332 ms4 KB18 KB200text/cssStylesheet
https://www.gstatic.com/images/branding/product/1x/translate_24dp.png
333 ms355 ms1 KB1 KB200image/pngImage
https://www.google.com/images/cleardot.gif
333 ms355 ms0 KB0 KB200image/gifImage
http://pangea2.group/translate/32.png
368 ms396 ms0 KB0 KB200image/pngImage
https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
368 ms396 ms60 KB59 KB200font/woff2Font
Serve static assets with an efficient cache policy - 10 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://pangea2.group/pang3.png
0 ms17 KB
http://pangea2.group/general.png
0 ms11 KB
http://pangea2.group/merged.png
0 ms6 KB
http://pangea2.group/translate/style.css
0 ms2 KB
http://pangea2.group/translate/32.png
0 ms0 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
3600000 ms4 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
3600000 ms4 KB
https://translate.googleapis.com/translate_static/js/element/main.js
3600000 ms2 KB
http://trafficadbar.com/images/home_logo_88.png
5184000000 ms2 KB
http://trafficadbar.com/bar/show.js
5184000000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
75 ms
7 ms
159 ms
6 ms
166 ms
5 ms
172 ms
19 ms
193 ms
7 ms
290 ms
6 ms
307 ms
45 ms
352 ms
7 ms
374 ms
11 ms
385 ms
10 ms
415 ms
16 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
28 ms
JavaScript execution time - 0.2 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
708 ms18 ms6 ms
https://translate.googleapis.com/element/TE_20190506_00/e/js/element/element_main.js
182 ms139 ms29 ms
Remove unused CSS - Potential savings of 0 KB
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.

URL
SizePotential Savings
https://fonts.googleapis.com/icon?family=Material+Icons
0 KB0 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
4 KB4 KB
Avoids enormous network payloads - Total size was 216 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://translate.googleapis.com/element/TE_20190506_00/e/js/element/element_main.js
87 KB
https://fonts.gstatic.com/s/materialicons/v47/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
60 KB
http://pangea2.group/pang3.png
17 KB
http://pangea2.group/general.png
11 KB
http://pangea2.group/
10 KB
http://pangea2.group/merged.png
6 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
4 KB
https://translate.googleapis.com/translate_static/css/translateelement.css
4 KB
http://trafficadbar.com/images/home_logo_88.png
2 KB
https://www.gstatic.com/images/branding/product/2x/translate_24dp.png
2 KB
Minimizes main-thread work - 1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Style & Layout
287 ms
Other
260 ms
Script Evaluation
195 ms
Rendering
130 ms
Parse HTML & CSS
56 ms
Script Parsing & Compilation
45 ms
Serve images in next-gen formats - Potential savings of 11 KB
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.

URL
SizePotential Savings
http://pangea2.group/pang3.png
16 KB11 KB
Avoids an excessive DOM size - 249 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
249
Maximum DOM Depth
26
Maximum Child Elements
24
Keep request counts low and transfer sizes small - 21 requests • 216 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
21216 KB
Script
592 KB
Font
160 KB
Image
841 KB
Document
211 KB
Stylesheet
411 KB
Other
11 KB
Media
00 KB
Third-party
15170 KB
Server response times are low (TTFB) - Root document took 60 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.

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.

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.

Minimize Critical Requests Depth - 5 chains 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 908 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <span>Select Language</span> falls outside the viewport.
The element <img src="https://www.go…s/cleardot.gif"> falls outside the viewport.
The element <span>​</span> falls outside the viewport.
The element <img src="https://www.go…s/cleardot.gif"> falls outside the viewport.
The element <span> falls outside the viewport.
The element <font>#2</font> falls outside the viewport.
The element <img src="merged.png"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <font>.</font> falls outside the viewport.
The element <input type="text" name="name3"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <input type="text" name="email3"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <input type="text" name="user3"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <input type="password" name="pass3"> falls outside the viewport.
The element <br> falls outside the viewport.
The element <br> falls outside the viewport.
The element <button class="textshadow1">JOIN NOW</button> falls outside the viewport.
The element <br> falls outside the viewport.
The element <span>GDPR/Privacy Policy</span> falls outside the viewport.
The element <span>HOW DOES THIS WORK?</span> falls outside the viewport.
The element <b>Just Email.</b> falls outside the viewport.
The element <b>no problem.</b> falls outside the viewport.
The element <b>no problem.</b> falls outside the viewport.
The element <u>PANGEA #1</u> falls outside the viewport.
The element <span>&quot;PANGEA&quot;</span> falls outside the viewport.
The element <font>Maryanne Myers…tising Network</font> falls outside the viewport.
The element <font>POLICIES</font> falls outside the viewport.
The element <font>TERMS</font> falls outside the viewport.
The element <font>CONTACT</font> falls outside the viewport.
The element <iframe src="//trafficadbar…pangea2.group/"> falls outside the viewport.

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://pangea2.group/translate/style.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://pangea2.group/general.png (expiration not specified)
http://pangea2.group/merged.png (expiration not specified)
http://pangea2.group/pang3.png (expiration not specified)
http://pangea2.group/translate/32.png (expiration not specified)
http://pangea2.group/translate/style.css (expiration not specified)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 8KiB (67% reduction).

Compressing http://pangea2.group/ could save 6.6KiB (68% reduction).
Compressing http://pangea2.group/translate/style.css could save 1.2KiB (64% reduction).
Compressing http://trafficadbar.com/bar/show.js could save 215B (43% reduction).

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 338B (19% reduction).

Minifying http://pangea2.group/translate/style.css could save 338B (19% reduction).

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 266B (13% reduction).

Compressing http://trafficadbar.com/images/home_logo_88.png could save 266B (13% reduction).
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does pangea2.group use compression?

pangea2.group does not use compression.
Original size: 9.62 KB
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

pangea2.group supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: pangea2.group
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Apr 27 02:32:55 2019 GMT
Valid until: Jul 26 02:32:55 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

pangea2.group does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 09 Jun 2019 08:58:46 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
X-Powered-By: PleskLin
Transfer-Encoding: chunked
Content-Type: text/html

+ DNS Lookup

Type Ip Target TTL
A 64.34.196.230 3600
TXT 3600
SOA 3600
Mname ns1.peer1.net
Rname hostmaster.pangea2.group
Serial Number 24
Refresh 25200
Retry 3600
Expire 172800
Minimum TTL 0
MX pangea2.group 3600
NS ns2.peer1.net 3600
NS ns1.peer1.net 3600

+ Whois Lookup

Domain Created:
2018-10-16
Domain Age:
7 months 24 days  
WhoIs:
 

whois lookup at whois.donuts.co...
Domain Name: pangea2.group
Registry Domain ID: e4f848eae11b47ce8aee25908a0ca86d-DONUTS
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2018-10-21T19:28:38Z
Creation Date: 2018-10-16T19:27:40Z
Registry Expiry Date: 2019-10-16T19:27:40Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization:
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: FL
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: 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: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: 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: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.peer1.net
Name Server: ns2.peer1.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-06-09T08:59:21Z <<<

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

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no cir***stances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar’s own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Last update was 302 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with pangea2.group in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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!
pangea2.group widget