Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 59% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

caperz.us

caperz.us - This website is for sale! - caperz Resources and Information.

Page Load Speed

1.7 sec in total

First Response

656 ms

Resources Loaded

932 ms

Page Rendered

73 ms

caperz.us screenshot

About Website

Visit caperz.us now to see the best up-to-date Caperz content for Indonesia and also check out these interesting facts you probably never knew about caperz.us

This website is for sale! caperz.us is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, caperz.us has it all...

Visit caperz.us

Key Findings

We analyzed Caperz.us page load time and found that the first response time was 656 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

caperz.us performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

caperz.us

656 ms

ww1.caperz.us

62 ms

caf.js

64 ms

2.5940ae1c.chunk.js

48 ms

main.4e219663.chunk.js

46 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Caperz.us, 40% (2 requests) were made to Img1.wsimg.com and 20% (1 request) were made to Ww1.caperz.us. The less responsive or slowest element that took the longest time to load (656 ms) belongs to the original domain Caperz.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 kB (2%)

Content Size

76.6 kB

After Optimization

75.3 kB

In fact, the total size of Caperz.us main page is 76.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 74.0 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 1.3 kB

  • Original 2.6 kB
  • After minification 2.6 kB
  • After compression 1.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.3 kB or 52% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 74.0 kB
  • After minification 74.0 kB
  • After compression 74.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caperz. According to our analytics all requests are already optimized.

Accessibility Review

caperz.us accessibility score

85

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

caperz.us best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

caperz.us SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caperz.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Caperz.us main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Caperz. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: