Your Website Score is
SEO Rank : 59 Website URL: prettyuglylittleliar.net Last Updated: 5 months
Success
62% of passed verification steps
Warning
23% of total warning
Errors
15% of total errors, require fast action
Share
Estimation Traffic and Earnings
1,572
Unique Visits
Daily
2,908
Pages Views
Daily
$6
Income
Daily
44,016
Unique Visits
Monthly
82,878
Pages Views
Monthly
$150
Income
Monthly
509,328
Unique Visits
Yearly
977,088
Pages Views
Yearly
$1,584
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 45%
Domain Authority
Domain Authority 55%
Moz Rank
4.5/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
32 Characters
FORUMS - PRETTY UGLY LITTLE LIAR
Meta Description
95 Characters
Pretty Ugly Little Liar (PULL) is a censorship-free forum about popular Internet personalities.
Effective URL
32 Characters
https://prettyuglylittleliar.net
Excerpt
Page content
Forums - Pretty Ugly Little Liar
Jump to content
Existing user? Sign In
Sign In
Remember me
Not recommended on shared computers
Sign in anonymously
Sign In
...
Meta Keywords
23 Detected
pretty ugly little liar
pretty ugly little liars
prettyuglylittleliar
prettyuglylittleliars
prettyuglylittleliar forum
pull
pull forum
snowflakes
gossip
dakotakoti
kiki kannibal
dakota rose
dakota koti
kanadajin3
venus angelic
margaret palermo
wylona hayashi
taylor r
johanna hersstedt
jessica nigri
annedere
annearchyy
ostrenga
Google Preview
Your look like this in google search result
FORUMS - PRETTY UGLY LITTLE LIAR
https://prettyuglylittleliar.net
Pretty Ugly Little Liar (PULL) is a censorship-free forum about popular Internet personalities.
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~63.69 KB
Code Size: ~57 KB
Text Size: ~6.69 KB Ratio: 10.50%
Social Data
Desktop
First CPU Idle
1.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 0 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
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive
1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests
19 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
Serve static assets with an efficient cache policy
41 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short
Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
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
First Contentful Paint
1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Preload key requests
Potential savings of 320 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
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
Efficiently encode images
Potential savings of 18 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small
50 requests • 1,722 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index
1.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay
40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Remove unused CSS
Potential savings of 29 KiB
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
Cumulative Layout Shift
0.271
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimizes main-thread work
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads
Total size was 1,722 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint
2.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Remove unused JavaScript
Potential savings of 74 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size
720 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)
Eliminate render-blocking resources
Potential savings of 1,120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats
Potential savings of 1,145 KiB
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
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
First Meaningful Paint
1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Properly size images
Potential savings of 209 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Mobile
Total Blocking Time
230 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Tap targets are not sized appropriately
75% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
First CPU Idle
4.4 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/).
Avoid chaining critical requests
18 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
Properly size images
Potential savings of 312 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Minimizes main-thread work
1.9 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
50 requests • 1,719 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
First Contentful Paint
4.4 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources
Potential savings of 3,310 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoids enormous network payloads
Total size was 1,719 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused CSS
Potential savings of 31 KiB
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
Document uses legible font sizes
100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Minimize third-party usage
Third-party code blocked the main thread for 40 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
Avoids an excessive DOM size
720 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)
Remove unused JavaScript
Potential savings of 74 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Max Potential First Input Delay
120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Meaningful Paint
4.4 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint
11.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
JavaScript execution time
0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Estimated Input Latency
30 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
Preload key requests
Potential savings of 2,430 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Efficiently encode images
Potential savings of 18 KiB
Optimized images load faster and consume less cellular data
Serve static assets with an efficient cache policy
41 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint (3G)
8759 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Serve images in next-gen formats
Potential savings of 1,145 KiB
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
Avoid long main-thread tasks
5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index
4.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Initial server response time was short
Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive
5.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Warning! Your site not 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
Congratulations! You are using your H1 and H2 tags in your site
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
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| https://prettyuglylittleliar.net/search/ | Internal Link | 200 |
| https://prettyuglylittleliar.net/ | Internal Link | 200 |
| Existing user? Sign In | Internal Link | 307 |
| Forgot your password? | Internal Link | 200 |
| All Content | Internal Link | 301 |
| Activity Stream | Internal Link | 200 |
| Guidelines | Internal Link | 200 |
| Staff | Internal Link | 200 |
| Status Updates | Internal Link | 200 |
| Online Users | Internal Link | 200 |
| Go to Nyx's profile | Internal Link | 200 |
| PULL Archiving | Internal Link | 200 |
| Pretty Ugly Little Liar | Internal Link | 200 |
| News & Announcements | Internal Link | 200 |
| Pull Archiving | Internal Link | 301 |
| Go to last post | Internal Link | 301 |
| Introduce Yourself | Internal Link | 200 |
| Go to fabienne's profile | Internal Link | 200 |
| hellooo | Internal Link | 301 |
| Go to last post | Internal Link | 301 |
Alexa Rank
Local Rank: O / Users: 80.5% / PageViews: 67.8%
78,126
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| prettyuglylittleliar.co | Available Buy Now! |
| prettyuglylittleliar.us | Available Buy Now! |
| prettyuglylittleliar.com | Available Buy Now! |
| prettyuglylittleliar.org | Already Registered |
| prettyuglylittleliar.net | Already Registered |
| pettyuglylittleliar.net | Available Buy Now! |
| lrettyuglylittleliar.net | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Wed, 05 Aug 2020 05:41:08 GMT
content-type: text/html;charset=UTF-8
set-cookie: __cfduid=d54dc656765cbbefa572e5a16c3e1997c1596606067; expires=Fri, 04-Sep-20 05:41:07 GMT; path=/; domain=.prettyuglylittleliar.net; HttpOnly; SameSite=Lax; Secure
x-powered-by: PHP/5.6.18-1~dotdeb+7.1
set-cookie: ips4_IPSSessionFront=nbtr98hcngjfniivrab831q5v3; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
x-xss-protection: 0
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
referrer-policy: same-origin
cf-cache-status: DYNAMIC
cf-request-id: 045ebc4cdc0000983fa61fc200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
strict-transport-security: max-age=2592000
server: cloudflare
cf-ray: 5bde2ff49b5f983f-LAX
content-encoding: gzip
Click to Add/Show Comments