Abase.Me - Info abase.me

abase.me receives about 227 unique visitors and 454 (2.00 per visitor) page views per day which should earn about $1.85/day from advertising revenue. Estimated site value is $1,351.08. According to Alexa Traffic Rank abase.me is ranked number 4,501,119 in the world and 5.0E-6% of global Internet users visit it. Site is hosted in Homburg, Saarland, 66424, Germany and links to network IP address 185.53.179.6. This server doesn't support HTTPS and doesn't support HTTP/2.

About - abase.me


Technologies used on Website

Font Scripts
Google Font API
Web Servers
Nginx
Reverse Proxy
Nginx

abase.me Profile

Title: abase.me
Keywords: av abase
Last update was 10 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is abase.me?

227 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
227
Monthly Unique Visitors:
5,448
Pages per Visit:
2.00
Daily Pageviews:
454
Alexa Rank:
4,501,119 visit alexa
Alexa Reach:
5.0E-6%   (of global internet users)
Avg. visit duration:
00:03
Bounce rate:
100.00%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

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

Visitors by country

Users%Pageviews%Rank
United States 83.9%85.9%622184

Where do visitors go on this site?

Reach%Pageviews%PerUser
abase.me
100.00%100.00%1

Competitive Data

SEMrush
Domain:
  abase.me
Rank:
(Rank based on keywords, cost and organic traffic)
  2,764,695
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  17
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:
  3
Page Authority:
  29
MozRank:
  3

+ How socially engaged is abase.me?

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:
abase.me
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:
abase.me
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 abase.me can earn?

Daily Revenue:
$1.85
Monthly Revenue:
$55.50
Yearly Revenue:
$675.25
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 390$4.47

How much money do abase.me lose due to Adblock?

Daily Revenue Loss:
$0.81
Monthly Revenue Loss:
$24.15
Yearly Revenue Loss:
$293.89
Daily Pageviews Blocked:
70
Monthly Pageviews Blocked:
2,106
Yearly Pageviews Blocked:
25,622
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 70$0.81

How much is abase.me worth?

Website Value:
$1,351.08

+ Where is abase.me hosted?

Server IP:
185.53.179.6
ASN:
AS61969 
ISP:
Team Internet AG 
Server Location:
Homburg
Saarland, SL
66424
Germany, DE
 

Other sites hosted on 185.53.179.6

+ How fast does abase.me load?

Average Load Time:
(653 ms) 91 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

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 90 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.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 40 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 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.1 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.9 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.9 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.

Minimize third-party usage - Third-party code blocked the main thread for 210 ms
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.

Third-Party
SizeMain-Thread Blocking Time
134 KB144 ms
24 KB69 ms
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
359 ms
6 ms
392 ms
170 ms
566 ms
7 ms
680 ms
53 ms
734 ms
139 ms
877 ms
7 ms
886 ms
7 ms
895 ms
11 ms
912 ms
90 ms
1002 ms
87 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/poppins/v9/pxiByp8kv8JHgFVrLDz8Z1xlFQ.woff2
4 ms
https://fonts.gstatic.com/s/poppins/v9/pxiEyp8kv8JHgFVrJJfecg.woff2
3 ms
https://fonts.gstatic.com/s/poppins/v9/pxiEyp8kv8JHgFVrJJfecg.woff2
3 ms
JavaScript execution time - 0.5 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
https://www.google.com/adsense/domains/caf.js
233 ms209 ms7 ms
http://www.google.com/adsense/domains/caf.js
154 ms146 ms4 ms
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
120 ms119 ms1 ms
Other
80 ms9 ms2 ms
Avoids enormous network payloads - Total size was 193 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.com/adsense/domains/caf.js
57 KB
http://www.google.com/adsense/domains/caf.js
56 KB
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
16 KB
https://fonts.gstatic.com/s/poppins/v9/pxiEyp8kv8JHgFVrJJfecg.woff2
8 KB
https://fonts.gstatic.com/s/poppins/v9/pxiEyp8kv8JHgFVrJJfecg.woff2
8 KB
https://fonts.gstatic.com/s/poppins/v9/pxiByp8kv8JHgFVrLDz8Z1xlFQ.woff2
8 KB
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-teaminternet09_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&terms=Car%2520Insurance%2CInternet%2Cmother%2CAARP%2CBase%2COnline%2520Colleges&swp=as-drid-2114370249365848&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404&format=r5%7Cs&num=0&output=afd_ads&domain_name=abase.me&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1581688962687&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=829&frm=0&uio=ff2sa16fa2sl1sr1-st24sa14lt34-&jsv=12885&rurl=http%3A%2F%2Fabase.me%2F
7 KB
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7 KB
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
6 KB
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
6 KB
Minimizes main-thread work - 0.6 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
Script Evaluation
515 ms
Other
47 ms
Style & Layout
33 ms
Script Parsing & Compilation
17 ms
Parse HTML & CSS
8 ms
Rendering
6 ms
Garbage Collection
6 ms
Avoids an excessive DOM size - 35 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
35
Maximum DOM Depth
8
Maximum Child Elements
14
Keep request counts low and transfer sizes small - 22 requests • 193 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
22193 KB
Script
5132 KB
Font
325 KB
Image
317 KB
Document
314 KB
Stylesheet
56 KB
Other
31 KB
Media
00 KB
Third-party
18188 KB
Eliminate render-blocking resources - Potential savings of 450 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.google.com/adsense/domains/caf.js
56 KB310
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
1 KB190
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
1 KB190
https://fonts.googleapis.com/css?family=Poppins:300
1 KB230
Enable text compression - Potential savings of 5 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
6 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://abase.me/
0 ms336 ms5 KB9 KB200text/htmlDocument
http://www.google.com/adsense/domains/caf.js
347 ms362 ms56 KB158 KB200text/javascriptScript
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
347 ms363 ms1 KB1 KB200text/cssStylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
347 ms364 ms1 KB1 KB200text/cssStylesheet
https://fonts.googleapis.com/css?family=Poppins:300
347 ms365 ms1 KB1 KB200text/cssStylesheet
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
348 ms364 ms7 KB6 KB200application/javascriptScript
http://abase.me/track.php?domain=abase.me&toggle=browserjs&uid=MTU4MTY4ODk2Mi4zNDA5OmMxMjM0YWQyYjdmNDc1M2JiYmZhY2FmOTNlMzU1OWEzYjRlNDMwNjQ0MjJiZTU3ZDU0OWQ2YzZjZjRkYzk5Mzg6NWU0NmE4ODI1MzNkNw%3D%3D
386 ms503 ms0 KB0 KB200text/htmlXHR
http://abase.me/ls.php
506 ms618 ms0 KB0 KB201text/javascriptXHR
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
517 ms565 ms16 KB15 KB200image/pngImage
https://fonts.gstatic.com/s/poppins/v9/pxiByp8kv8JHgFVrLDz8Z1xlFQ.woff2
519 ms523 ms8 KB8 KB200font/woff2Font
https://www.google.com/afs/ads/i/iframe.html
532 ms539 ms2 KB1 KB200text/htmlDocument
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-teaminternet09_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&terms=Car%2520Insurance%2CInternet%2Cmother%2CAARP%2CBase%2COnline%2520Colleges&swp=as-drid-2114370249365848&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404&format=r5%7Cs&num=0&output=afd_ads&domain_name=abase.me&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1581688962687&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=829&frm=0&uio=ff2sa16fa2sl1sr1-st24sa14lt34-&jsv=12885&rurl=http%3A%2F%2Fabase.me%2F
539 ms623 ms7 KB9 KB200text/htmlDocument
http://www.gstatic.com/domainads/tracking/caf.gif?ts=1581688962678&rid=6163920
542 ms547 ms0 KB0 KB200image/gifImage
https://www.google.com/adsense/domains/caf.js
633 ms652 ms57 KB158 KB200text/javascriptScript
https://fonts.googleapis.com/css?family=Poppins
682 ms699 ms1 KB1 KB200text/cssStylesheet
https://fonts.googleapis.com/css?family=Poppins
702 ms719 ms1 KB1 KB200text/cssStylesheet
https://www.gstatic.com/domainads/images/chevron-white.png
709 ms712 ms1 KB0 KB200image/pngImage
http://abase.me/track.php?domain=abase.me&caf=1&toggle=answercheck&answer=yes&uid=MTU4MTY4ODk2Mi4zNDA5OmMxMjM0YWQyYjdmNDc1M2JiYmZhY2FmOTNlMzU1OWEzYjRlNDMwNjQ0MjJiZTU3ZDU0OWQ2YzZjZjRkYzk5Mzg6NWU0NmE4ODI1MzNkNw%3D%3D
716 ms853 ms0 KB0 KB200text/htmlXHR
https://fonts.gstatic.com/s/poppins/v9/pxiEyp8kv8JHgFVrJJfecg.woff2
863 ms866 ms8 KB8 KB200font/woff2Font
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
865 ms869 ms6 KB12 KB200text/javascriptScript
https://fonts.gstatic.com/s/poppins/v9/pxiEyp8kv8JHgFVrJJfecg.woff2
868 ms871 ms8 KB8 KB200font/woff2Font
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
892 ms892 ms6 KB12 KB200text/javascriptScript
Uses efficient cache policy on static assets - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/img/arrows.png
0 ms16 KB
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0 ms7 KB
http://d1lxhc4jvstzrp.cloudfront.net/themes/cleanPeppermint_7a82f1f3/style.css
0 ms1 KB
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0 ms1 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.

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

Server response times are low (TTFB) - Root document took 340 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.


Page Speed (Google PageSpeed Insights) - Mobile

86
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 3.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 370 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 4.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 100 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) 5750 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 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.9 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 3.0 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 - 15 requests • 160 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
15160 KB
Script
5132 KB
Document
314 KB
Image
313 KB
Stylesheet
11 KB
Other
31 KB
Media
00 KB
Font
00 KB
Third-party
11154 KB
Eliminate render-blocking resources - Potential savings of 1,510 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.google.com/adsense/domains/caf.js
56 KB1080
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
1 KB630
Enable text compression - Potential savings of 5 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
6 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://abase.me/
0 ms368 ms5 KB9 KB200text/htmlDocument
http://www.google.com/adsense/domains/caf.js
378 ms395 ms56 KB158 KB200text/javascriptScript
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
378 ms420 ms1 KB2 KB200text/cssStylesheet
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
378 ms422 ms7 KB6 KB200application/javascriptScript
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
423 ms470 ms11 KB10 KB200image/pngImage
http://abase.me/track.php?domain=abase.me&toggle=browserjs&uid=MTU4MTY4ODk1Ni41NDI6NzgzODQzYmU1ZDU2NWYyMGM5MGU3ODkxYjI0MDZlODlhYWY1MGY4ZmY5YWZhZjhhYWYxNWFhMGZkYWNlYzg0Yzo1ZTQ2YTg3Yzg0NTk3
431 ms647 ms0 KB0 KB200text/htmlXHR
http://abase.me/ls.php
650 ms774 ms0 KB0 KB201text/javascriptXHR
https://www.google.com/afs/ads/i/iframe.html
665 ms670 ms2 KB1 KB200text/htmlDocument
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-mobile-teaminternet02_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&terms=Car%2520Insurance%2CInternet%2Cmother%2CAARP%2CBase%2COnline%2520Colleges&swp=as-drid-2114370249365848&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404&format=r5%7Cs&num=0&output=afd_ads&domain_name=abase.me&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1581688957004&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=286&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1st16sa13lt50-ff1fa1&jsv=12885&rurl=http%3A%2F%2Fabase.me%2F
671 ms755 ms7 KB9 KB200text/htmlDocument
http://www.gstatic.com/domainads/tracking/caf.gif?ts=1581688956996&rid=2916849
674 ms678 ms0 KB0 KB200image/gifImage
https://www.google.com/adsense/domains/caf.js
766 ms783 ms58 KB158 KB200text/javascriptScript
https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif
838 ms843 ms2 KB1 KB200image/gifImage
http://abase.me/track.php?domain=abase.me&caf=1&toggle=answercheck&answer=yes&uid=MTU4MTY4ODk1Ni41NDI6NzgzODQzYmU1ZDU2NWYyMGM5MGU3ODkxYjI0MDZlODlhYWY1MGY4ZmY5YWZhZjhhYWYxNWFhMGZkYWNlYzg0Yzo1ZTQ2YTg3Yzg0NTk3
844 ms955 ms0 KB0 KB200text/htmlXHR
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
961 ms964 ms6 KB12 KB200text/javascriptScript
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
975 ms978 ms6 KB12 KB200text/javascriptScript
Uses efficient cache policy on static assets - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
0 ms11 KB
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0 ms7 KB
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css
0 ms1 KB
https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif
82800000 ms2 KB
Reduce the impact of third-party code - Third-party code blocked the main thread for 1,680 ms
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.

Third-Party
SizeMain-Thread Blocking Time
134 KB860 ms
19 KB823 ms
0 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
389 ms
6 ms
423 ms
8 ms
441 ms
6 ms
448 ms
246 ms
697 ms
5 ms
777 ms
6 ms
811 ms
50 ms
862 ms
113 ms
980 ms
9 ms
995 ms
73 ms
1070 ms
70 ms
Reduce JavaScript execution time - 2.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
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
875 ms873 ms2 ms
https://www.google.com/adsense/domains/caf.js
781 ms689 ms27 ms
http://www.google.com/adsense/domains/caf.js
491 ms472 ms16 ms
Other
255 ms32 ms9 ms
http://abase.me/
108 ms91 ms7 ms
Avoids enormous network payloads - Total size was 160 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.google.com/adsense/domains/caf.js
58 KB
http://www.google.com/adsense/domains/caf.js
56 KB
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png
11 KB
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-mobile-teaminternet02_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&terms=Car%2520Insurance%2CInternet%2Cmother%2CAARP%2CBase%2COnline%2520Colleges&swp=as-drid-2114370249365848&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404&format=r5%7Cs&num=0&output=afd_ads&domain_name=abase.me&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-480&dt=1581688957004&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=286&frm=0&uio=ff2sa16fa2sl1sr1-ff1fa1st16sa13lt50-ff1fa1&jsv=12885&rurl=http%3A%2F%2Fabase.me%2F
7 KB
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7 KB
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
6 KB
https://www.google.com/js/bg/-ZHrKYMf9F8--MY-KPiYF6mBKpmd18QLRzrou_PReu4.js
6 KB
http://abase.me/
5 KB
https://www.google.com/afs/ads/i/iframe.html
2 KB
https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif
2 KB
Minimize main-thread work - 2.5 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
Script Evaluation
2172 ms
Other
155 ms
Style & Layout
76 ms
Script Parsing & Compilation
68 ms
Parse HTML & CSS
26 ms
Garbage Collection
19 ms
Rendering
17 ms
Avoids an excessive DOM size - 33 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
33
Maximum DOM Depth
5
Maximum Child Elements
15
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 370 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.

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 - 3 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) - v2

Suggestions Summary

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

Your page has 2 blocking script resources and 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.Remove render-blocking JavaScript:

http://www.google.com/adsense/domains/caf.js
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Optimize CSS Delivery of the following:

http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

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://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js (expiration not specified)
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/img/bg10wide.png (expiration not specified)
http://d1lxhc4jvstzrp.cloudfront.net/themes/MobileCleanBlack_93ab7840/style.css (expiration not specified)
http://www.google.com/adsense/domains/caf.js (60 minutes)
https://www.google.com/adsense/domains/caf.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 4.5KiB (73% reduction).

Compressing http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js could save 4.5KiB (73% reduction).

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="https://www.go…et02_3ph&amp;gl=US">Related Links</a> is close to 1 other tap targets .

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 1.6KiB (26% reduction).

Minifying http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js could save 1.6KiB (26% reduction).

Optimize images

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

Optimize the following images to reduce their size by 1KiB (93% reduction).

Compressing https://afs.googleusercontent.com/dp-teaminternet/uni_blank1.gif could save 1KiB (93% reduction).
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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 abase.me use compression?

abase.me use gzip compression.
Original size: 9.02 KB
Compressed size: 4.33 KB
File reduced by: 4.69 KB (52%)

+ 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

abase.me does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

abase.me does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Fri, 14 Feb 2020 14:02:19 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
X-Check: 3c12dc4d54f8e22d666785b733b0052100c53444
X-Language: english
X-Template: tpl_CleanPeppermintBlack_twoclick
X-Buckets: 
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_iKyD+EK+TzTRLOQlGlDsQYpSK/O+l9QZHQsVjpdrZSsbePSS944RYjpFdP9lhYcAVh16uEA5pj1iqArrbsnu+Q==
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
TXT 3600
MX mail.h-email.net 3600
SOA 3600
Mname ns1.parkingcrew.net
Rname hostmaster.abase.me
Serial Number 1581688000
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 0
A 185.53.179.6 582
NS ns2.parkingcrew.net 3582
NS ns1.parkingcrew.net 3582

+ Whois Lookup

Domain Created:
2018-07-09
Domain Age:
1 years 7 months 5 days  
WhoIs:
 

whois lookup at whois.nic.me...
Domain Name: ABASE.ME
Registry Domain ID: D425500000049127059-AGRS
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: http://www.dynadot.com
Updated Date: 2018-11-27T03:32:29Z
Creation Date: 2018-07-09T01:05:51Z
Registry Expiry Date: 2020-07-09T01:05:51Z
Registrar Registration Expiration Date:
Registrar: Dynadot, LLC
Registrar IANA ID: 472
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6502620100
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registrant Organization: email
Registrant State/Province: Harju
Registrant Country: EE
Name Server: NS1.PARKINGCREW.NET
Name Server: NS2.PARKINGCREW.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2020-02-14T14:01:47Z <<<

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

Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by The Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data 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 data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Registry Operator reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 10 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

webmail.bcferries.com
22 secs
geniusbaba.co.uk
40 secs
indiaservicepvt.com
56 secs
reallifecam.vip
1 min
expansion.mx
1 min
xhamster.com
1 min
jibjab.com
1 min
genint.com
1 min
gempac.in
2 mins
cocgemsgiveaways.com
2 mins
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!
abase.me widget