Candydoll.Lv candydoll.lv

part10.Candydoll.Lv

part10.candydoll.lv receives about 2,715 unique visitors and 10,859 (4.00 per visitor) page views per day which should earn about $44.30/day from advertising revenue. Estimated site value is $18,368.10. According to Alexa Traffic Rank part10.candydoll.lv is ranked number 292,511 in the world and 0.00016% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.24.96.192. This server supports HTTPS and HTTP/2.

About - part10.candydoll.lv


Technologies used on Website

CDN
CloudFlare

part10.candydoll.lv Profile

Title: CANDY DOLL - PART 10
Last update was 166 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is part10.candydoll.lv?

2.7K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
2,715
Monthly Unique Visitors:
65,160
Pages per Visit:
4.00
Daily Pageviews:
10,859
Alexa Rank:
292,511 visit alexa
Alexa Reach:
0.00016%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

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

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  part10.candydoll.lv
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
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 part10.candydoll.lv?

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:
candydoll.lv
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:
candydoll.lv
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 part10.candydoll.lv can earn?

Daily Revenue:
$44.30
Monthly Revenue:
$1,329.00
Yearly Revenue:
$16,169.50
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do part10.candydoll.lv lose due to Adblock?

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

Daily revenue loss by country

Currently Not Available

How much is part10.candydoll.lv worth?

Website Value:
$18,368.10

+ Where is part10.candydoll.lv hosted?

Server IP:
104.24.96.192
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.24.96.192

+ How fast does part10.candydoll.lv load?

Average Load Time:
(1729 ms) 50 % 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 SLOW 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.

First Contentful Paint (FCP)3.2s 36% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 36% 48% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 48% 15% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 15%
First Input Delay (FID)18ms 98% of loads for this page have a fast (<50ms) First Input Delay (FID) 98% 1% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)2.6s 43% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 43% 46% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 46% 10% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 10%
First Input Delay (FID)17ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.3 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.3 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.3 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 50 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://part10.candydoll.lv/images/layout.css
3 KB70
Efficiently encode images - Potential savings of 89 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://part10.candydoll.lv/images/top-img_05.jpg
97 KB26 KB
http://part10.candydoll.lv/images/top-img_06.jpg
95 KB25 KB
http://part10.candydoll.lv/images/top-img_03.jpg
74 KB19 KB
http://part10.candydoll.lv/images/top-img_04.jpg
74 KB19 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://part10.candydoll.lv/
0 ms414 ms3 KB6 KB200text/htmlDocument
http://part10.candydoll.lv/images/layout.css
431 ms453 ms3 KB16 KB200text/cssStylesheet
http://part10.candydoll.lv/images/top_index_header.png
431 ms455 ms2 KB2 KB200image/pngImage
http://part10.candydoll.lv/images/top-img-side_01.png
431 ms453 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/top-img.jpg
457 ms487 ms111 KB111 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_03.jpg
460 ms500 ms74 KB74 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_04.jpg
460 ms492 ms74 KB74 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_05.jpg
460 ms492 ms98 KB97 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_06.jpg
460 ms493 ms95 KB95 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img-side_02.png
460 ms482 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_01.png
461 ms515 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_02.png
461 ms507 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_03.png
461 ms525 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_04.png
461 ms516 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_SAMPLE.gif
461 ms510 ms3 KB3 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_members.gif
461 ms519 ms3 KB2 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_entrance.gif
461 ms556 ms2 KB2 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_footer_06.png
462 ms543 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_07.png
462 ms531 ms1 KB1 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_08.png
462 ms555 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_09.png
462 ms537 ms1 KB1 KB200image/pngImage
http://part10.candydoll.lv/images/copylight.png
462 ms549 ms6 KB5 KB200image/pngImage
http://part10.candydoll.lv/images/bgblack.gif
465 ms549 ms1 KB1 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_footer_05.png
467 ms559 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif
561 ms583 ms3 KB3 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_entry-on.gif
561 ms588 ms1 KB0 KB404text/htmlImage
http://part10.candydoll.lv/images/TOP_entrance-on.gif
562 ms586 ms2 KB2 KB200image/gifImage
http://part10.candydoll.lv/images/copylight_xmas_on.png
562 ms583 ms1 KB0 KB404text/htmlImage
Serve static assets with an efficient cache policy - 25 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://part10.candydoll.lv/images/top-img.jpg
14400000 ms111 KB
http://part10.candydoll.lv/images/top-img_05.jpg
14400000 ms98 KB
http://part10.candydoll.lv/images/top-img_06.jpg
14400000 ms95 KB
http://part10.candydoll.lv/images/top-img_03.jpg
14400000 ms74 KB
http://part10.candydoll.lv/images/top-img_04.jpg
14400000 ms74 KB
http://part10.candydoll.lv/images/copylight.png
14400000 ms6 KB
http://part10.candydoll.lv/images/layout.css
14400000 ms3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif
14400000 ms3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE.gif
14400000 ms3 KB
http://part10.candydoll.lv/images/TOP_members.gif
14400000 ms3 KB
http://part10.candydoll.lv/images/top_index_header.png
14400000 ms2 KB
http://part10.candydoll.lv/images/TOP_entrance-on.gif
14400000 ms2 KB
http://part10.candydoll.lv/images/TOP_entrance.gif
14400000 ms2 KB
http://part10.candydoll.lv/images/TOP_footer_07.png
14400000 ms1 KB
http://part10.candydoll.lv/images/bgblack.gif
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_09.png
14400000 ms1 KB
http://part10.candydoll.lv/images/top-img-side_02.png
14400000 ms1 KB
http://part10.candydoll.lv/images/top-img-side_01.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_05.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_08.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_04.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_06.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_02.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_03.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_01.png
14400000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
439 ms
12 ms
479 ms
11 ms
491 ms
14 ms
509 ms
5 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
84 ms5 ms1 ms
Remove unused CSS - Potential savings of 3 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
http://part10.candydoll.lv/images/layout.css
3 KB3 KB
Avoids enormous network payloads - Total size was 492 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://part10.candydoll.lv/images/top-img.jpg
111 KB
http://part10.candydoll.lv/images/top-img_05.jpg
98 KB
http://part10.candydoll.lv/images/top-img_06.jpg
95 KB
http://part10.candydoll.lv/images/top-img_03.jpg
74 KB
http://part10.candydoll.lv/images/top-img_04.jpg
74 KB
http://part10.candydoll.lv/images/copylight.png
6 KB
http://part10.candydoll.lv/images/layout.css
3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif
3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE.gif
3 KB
http://part10.candydoll.lv/images/TOP_members.gif
3 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
42 ms
Style & Layout
17 ms
Rendering
10 ms
Parse HTML & CSS
9 ms
Script Evaluation
6 ms
Script Parsing & Compilation
2 ms
Serve images in next-gen formats - Potential savings of 204 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://part10.candydoll.lv/images/top-img_05.jpg
97 KB50 KB
http://part10.candydoll.lv/images/top-img_06.jpg
95 KB47 KB
http://part10.candydoll.lv/images/top-img_03.jpg
74 KB43 KB
http://part10.candydoll.lv/images/top-img_04.jpg
74 KB42 KB
http://part10.candydoll.lv/images/top-img.jpg
111 KB21 KB
Avoids an excessive DOM size - 56 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
56
Maximum DOM Depth
8
Maximum Child Elements
7
Keep request counts low and transfer sizes small - 28 requests • 492 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
28492 KB
Image
26486 KB
Stylesheet
13 KB
Document
13 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Server response times are low (TTFB) - Root document took 410 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

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

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

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

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

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

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

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

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

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

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

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) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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.

First Contentful Paint (FCP)2.7s 36% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 37% 50% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 50% 12% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 12%
First Input Delay (FID)292ms 1% of loads for this page have a fast (<50ms) First Input Delay (FID) 1% 76% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 76% 21% of loads for this page have a slow (>250ms) First Input Delay (FID) 21%

Origin Data

All pages served from this origin have an SLOW 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.

First Contentful Paint (FCP)2.6s 37% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 37% 50% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 50% 11% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 11%
First Input Delay (FID)309ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 1% 76% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 76% 22% of loads for this page have a slow (>250ms) First Input Delay (FID) 22%

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 1560 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 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.8 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.8 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.

Serve static assets with an efficient cache policy - 25 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://part10.candydoll.lv/images/top-img.jpg
14400000 ms111 KB
http://part10.candydoll.lv/images/top-img_05.jpg
14400000 ms98 KB
http://part10.candydoll.lv/images/top-img_06.jpg
14400000 ms95 KB
http://part10.candydoll.lv/images/top-img_03.jpg
14400000 ms74 KB
http://part10.candydoll.lv/images/top-img_04.jpg
14400000 ms74 KB
http://part10.candydoll.lv/images/copylight.png
14400000 ms6 KB
http://part10.candydoll.lv/images/layout.css
14400000 ms3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif
14400000 ms3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE.gif
14400000 ms3 KB
http://part10.candydoll.lv/images/TOP_members.gif
14400000 ms3 KB
http://part10.candydoll.lv/images/top_index_header.png
14400000 ms2 KB
http://part10.candydoll.lv/images/TOP_entrance-on.gif
14400000 ms2 KB
http://part10.candydoll.lv/images/TOP_entrance.gif
14400000 ms2 KB
http://part10.candydoll.lv/images/TOP_footer_07.png
14400000 ms1 KB
http://part10.candydoll.lv/images/bgblack.gif
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_09.png
14400000 ms1 KB
http://part10.candydoll.lv/images/top-img-side_02.png
14400000 ms1 KB
http://part10.candydoll.lv/images/top-img-side_01.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_05.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_08.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_04.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_06.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_02.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_03.png
14400000 ms1 KB
http://part10.candydoll.lv/images/TOP_footer_01.png
14400000 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
485 ms
12 ms
500 ms
6 ms
668 ms
9 ms
677 ms
6 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
301 ms17 ms3 ms
Remove unused CSS - Potential savings of 3 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
http://part10.candydoll.lv/images/layout.css
3 KB3 KB
Avoids enormous network payloads - Total size was 492 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://part10.candydoll.lv/images/top-img.jpg
111 KB
http://part10.candydoll.lv/images/top-img_05.jpg
98 KB
http://part10.candydoll.lv/images/top-img_06.jpg
95 KB
http://part10.candydoll.lv/images/top-img_03.jpg
74 KB
http://part10.candydoll.lv/images/top-img_04.jpg
74 KB
http://part10.candydoll.lv/images/copylight.png
6 KB
http://part10.candydoll.lv/images/layout.css
3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif
3 KB
http://part10.candydoll.lv/images/TOP_SAMPLE.gif
3 KB
http://part10.candydoll.lv/images/TOP_members.gif
3 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
184 ms
Parse HTML & CSS
37 ms
Rendering
31 ms
Style & Layout
29 ms
Script Evaluation
22 ms
Script Parsing & Compilation
6 ms
Serve images in next-gen formats - Potential savings of 204 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://part10.candydoll.lv/images/top-img_05.jpg
97 KB50 KB
http://part10.candydoll.lv/images/top-img_06.jpg
95 KB47 KB
http://part10.candydoll.lv/images/top-img_03.jpg
74 KB43 KB
http://part10.candydoll.lv/images/top-img_04.jpg
74 KB42 KB
http://part10.candydoll.lv/images/top-img.jpg
111 KB21 KB
Avoids an excessive DOM size - 56 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
56
Maximum DOM Depth
8
Maximum Child Elements
7
Keep request counts low and transfer sizes small - 28 requests • 492 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

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

URL
SizePotential Savings
http://part10.candydoll.lv/images/layout.css
3 KB180
Efficiently encode images - Potential savings of 89 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://part10.candydoll.lv/images/top-img_05.jpg
97 KB26 KB
http://part10.candydoll.lv/images/top-img_06.jpg
95 KB25 KB
http://part10.candydoll.lv/images/top-img_03.jpg
74 KB19 KB
http://part10.candydoll.lv/images/top-img_04.jpg
74 KB19 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://part10.candydoll.lv/
0 ms458 ms3 KB6 KB200text/htmlDocument
http://part10.candydoll.lv/images/layout.css
476 ms641 ms3 KB16 KB200text/cssStylesheet
http://part10.candydoll.lv/images/top_index_header.png
478 ms499 ms2 KB2 KB200image/pngImage
http://part10.candydoll.lv/images/top-img-side_01.png
478 ms500 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/top-img.jpg
501 ms658 ms111 KB111 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_03.jpg
501 ms677 ms74 KB74 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_04.jpg
645 ms686 ms74 KB74 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_05.jpg
645 ms683 ms98 KB97 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img_06.jpg
645 ms709 ms95 KB95 KB200image/jpegImage
http://part10.candydoll.lv/images/top-img-side_02.png
645 ms677 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_01.png
645 ms678 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_02.png
645 ms694 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_03.png
646 ms709 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_04.png
646 ms695 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_SAMPLE.gif
646 ms710 ms3 KB3 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_members.gif
646 ms710 ms3 KB2 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_entrance.gif
646 ms713 ms2 KB2 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_footer_06.png
646 ms714 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_07.png
647 ms731 ms1 KB1 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_08.png
647 ms727 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_footer_09.png
647 ms727 ms1 KB1 KB200image/pngImage
http://part10.candydoll.lv/images/copylight.png
647 ms726 ms6 KB5 KB200image/pngImage
http://part10.candydoll.lv/images/bgblack.gif
649 ms733 ms1 KB1 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_footer_05.png
650 ms732 ms1 KB0 KB200image/pngImage
http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif
736 ms769 ms3 KB3 KB200image/gifImage
http://part10.candydoll.lv/images/TOP_entry-on.gif
737 ms770 ms1 KB0 KB404text/htmlImage
http://part10.candydoll.lv/images/TOP_entrance-on.gif
737 ms765 ms2 KB2 KB200image/gifImage
http://part10.candydoll.lv/images/copylight_xmas_on.png
737 ms766 ms1 KB0 KB404text/htmlImage
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

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

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

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

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

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

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

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

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

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

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 460 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

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

Optimize the following images to reduce their size by 192.1KiB (42% reduction).

Compressing http://part10.candydoll.lv/images/top-img_05.jpg could save 47.7KiB (50% reduction).
Compressing http://part10.candydoll.lv/images/top-img_06.jpg could save 46.6KiB (50% reduction).
Compressing http://part10.candydoll.lv/images/top-img_03.jpg could save 36.7KiB (50% reduction).
Compressing http://part10.candydoll.lv/images/top-img_04.jpg could save 36.1KiB (49% reduction).
Compressing http://part10.candydoll.lv/images/top-img.jpg could save 19.7KiB (18% reduction).
Compressing http://part10.candydoll.lv/images/copylight.png could save 2.8KiB (52% reduction).
Compressing http://part10.candydoll.lv/images/TOP_SAMPLE-on.gif could save 642B (23% reduction).
Compressing http://part10.candydoll.lv/images/TOP_SAMPLE.gif could save 568B (21% reduction).
Compressing http://part10.candydoll.lv/images/TOP_entrance-on.gif could save 453B (22% reduction).
Compressing http://part10.candydoll.lv/images/TOP_entrance.gif could save 439B (22% reduction).
Compressing http://part10.candydoll.lv/images/TOP_members.gif could save 388B (16% reduction).

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://part10.candydoll.lv/images/TOP_SAMPLE-on.gif (4 hours)
http://part10.candydoll.lv/images/TOP_SAMPLE.gif (4 hours)
http://part10.candydoll.lv/images/TOP_entrance-on.gif (4 hours)
http://part10.candydoll.lv/images/TOP_entrance.gif (4 hours)
http://part10.candydoll.lv/images/TOP_footer_01.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_02.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_03.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_04.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_05.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_06.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_07.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_08.png (4 hours)
http://part10.candydoll.lv/images/TOP_footer_09.png (4 hours)
http://part10.candydoll.lv/images/TOP_members.gif (4 hours)
http://part10.candydoll.lv/images/bgblack.gif (4 hours)
http://part10.candydoll.lv/images/copylight.png (4 hours)
http://part10.candydoll.lv/images/layout.css (4 hours)
http://part10.candydoll.lv/images/top-img-side_01.png (4 hours)
http://part10.candydoll.lv/images/top-img-side_02.png (4 hours)
http://part10.candydoll.lv/images/top-img.jpg (4 hours)
http://part10.candydoll.lv/images/top-img_03.jpg (4 hours)
http://part10.candydoll.lv/images/top-img_04.jpg (4 hours)
http://part10.candydoll.lv/images/top-img_05.jpg (4 hours)
http://part10.candydoll.lv/images/top-img_06.jpg (4 hours)
http://part10.candydoll.lv/images/top_index_header.png (4 hours)

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

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://part10.candydoll.lv/images/layout.css

Reduce server response time

In our test, your server responded in 0.42 seconds.

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

Minify CSS

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

Minify CSS for the following resources to reduce their size by ***7B (23% reduction).

Minifying http://part10.candydoll.lv/images/layout.css could save ***7B (23% reduction) after compression.
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.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
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 part10.candydoll.lv use compression?

part10.candydoll.lv use gzip compression.
Original size: 6.23 KB
Compressed size: 2.23 KB
File reduced by: 4 KB (64%)

+ 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

part10.candydoll.lv supports HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

part10.candydoll.lv supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Wed, 04 Sep 2019 14:06:58 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=dea7a1c6a7f3c79e2f15b74bcf9e186691567606018; expires=Thu, 03-Sep-20 14:06:58 GMT; path=/; domain=.candydoll.lv; HttpOnly
Last-Modified: Thu, 23 Apr 2015 15:38:48 GMT
Vary: Accept-Encoding,User-Agent
Server: cloudflare
CF-RAY: 511086eecda6c63f-MSP
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
HINFO 3600

+ Whois Lookup

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

Currently Not Available
Last update was 166 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

whiskeddc.com
13 secs
***4arab***.com
16 secs
secure.advancepayroll.com.au
54 secs
telerano.markiza.sk
58 secs
carloszaldivar.com
1 min
area.ge
1 min
balkaniyum.tv
1 min
secr.teipir.gr
2 mins
xvideas.com
2 mins
softbox.tv
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!
part10.candydoll.lv widget