Your Website Score is
SEO Rank : 27 Website URL: phun.org Last Updated: 5 months
Success
55% of passed verification steps
Warning
15% of total warning
Errors
30% of total errors, require fast action
Share
Estimation Traffic and Earnings
5,464
Unique Visits
Daily
10,108
Pages Views
Daily
$22
Income
Daily
152,992
Unique Visits
Monthly
288,078
Pages Views
Monthly
$550
Income
Monthly
1,770,336
Unique Visits
Yearly
3,396,288
Pages Views
Yearly
$5,808
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 49%
Domain Authority
Domain Authority 55%
Moz Rank
4.9/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
46 Characters
PHUN.ORG / PHUN.COM - ADULT ENTERTAINMENT BLOG
Meta Description
81 Characters
phun.org - Our adult entertainment blog filled with funny links and ---y pictures
Effective URL
15 Characters
http://phun.org
Excerpt
Page content
phun.org / phun.com - Adult Entertainment Blog
...
Meta Keywords
15 Detected
Google Preview
Your look like this in google search result
PHUN.ORG / PHUN.COM - ADULT ENTERTAINMENT BLOG
http://phun.org
phun.org - Our adult entertainment blog filled with funny links and ---y pictures
Robots.txt
File Detected
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~138.39 KB
Code Size: ~98.66 KB
Text Size: ~39.73 KB Ratio: 28.71%
Social Data
Desktop
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids enormous network payloads
Total size was 1,785 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images
Potential savings of 7 KiB
Optimized images load faster and consume less cellular data
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
Cumulative Layout Shift
0.006
Cumulative Layout Shift measures the movement of visible elements within the viewport
Keep request counts low and transfer sizes small
180 requests • 1,785 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time
50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content
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
Minimizes main-thread work
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short
Root document took 430 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint
0.3 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy
50 resources found
A long cache lifetime can speed up repeat visits to your page
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
Defer offscreen images
Potential savings of 210 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Meaningful Paint
0.3 s
First Meaningful Paint measures when the primary content of a page is visible
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
Max Potential First Input Delay
160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize third-party usage
Third-party code blocked the main thread for 30 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
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](https://web.dev/first-cpu-idle/).
Time to Interactive
1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid an excessive DOM size
2,098 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)
Does not use HTTPS
154 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused JavaScript
Potential savings of 95 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Mobile
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Efficiently encode images
Potential savings of 7 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
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
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
Initial server response time was short
Root document took 340 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive
7.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid an excessive DOM size
2,098 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)
Serve static assets with an efficient cache policy
52 resources found
A long cache lifetime can speed up repeat visits to your page
JavaScript execution time
1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small
181 requests • 1,791 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Speed Index
2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle
4.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle/).
Minimize third-party usage
Third-party code blocked the main thread for 200 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
Cumulative Layout Shift
0.015
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimize main-thread work
3.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks
11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint (3G)
1693 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint
1.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Max Potential First Input Delay
280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads
Total size was 1,791 KiB
Large network payloads cost users real money and are highly correlated with long load times
Estimated Input Latency
50 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
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript
Potential savings of 95 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time
360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Does not use HTTPS
154 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| News | Internal Link | 200 |
| Forum | Internal Link | 301 |
| Specials | Internal Link | 200 |
| Fit Girls #5 | Internal Link | 200 |
| ---stars without make-up | Internal Link | 200 |
| Lineups | Internal Link | 200 |
| Galleries | Internal Link | 200 |
| Rachel Reynolds | Internal Link | 200 |
| Wild Anna | Internal Link | 200 |
| Sammie Pennington | Internal Link | 200 |
| Thong Of The Week Archive | Internal Link | 200 |
| Fansigns | Internal Link | 200 |
| Movies | Internal Link | 200 |
| Advertising | Internal Link | 200 |
| Link us: | Internal Link | 200 |
| Kate Moss | Internal Link | 200 |
| http://www.phun.org/galleries/kate_moss_nude_tim_walker/kate_moss_nude_tim_walker_01.jpg | Internal Link | 200 |
| http://www.phun.org/galleries/kate_moss_nude_tim_walker/kate_moss_nude_tim_walker_02.jpg | Internal Link | 200 |
| http://www.phun.org/galleries/kate_moss_nude_tim_walker/kate_moss_nude_tim_walker_03.jpg | Internal Link | 200 |
| http://www.phun.org/galleries/kate_moss_nude_tim_walker/kate_moss_nude_tim_walker_04.jpg | Internal Link | 200 |
Alexa Rank
647
Local Rank: DE / Users: 46.3% / PageViews: 70.8%14,252
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| phun.co | Available Buy Now! |
| phun.us | Available Buy Now! |
| phun.com | Already Registered |
| phun.org | Already Registered |
| phun.net | Available Buy Now! |
| pun.org | Already Registered |
| lhun.org | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 07 Aug 2020 02:33:28 GMT
Content-Type: text/html; charset=UTF-8
Keep-Alive: timeout=20
X-Powered-By: PHP/5.5.9-1ubuntu4.17
Expires: Sat, 08 Aug 2020 02:33:27 GMT
Content-Encoding: gzip
Set-Cookie: PHUN=SRV2; path=/
Cache-control: private
Click to Add/Show Comments