Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

original.rocks

我弄的 Tee

Page Load Speed

2.7 sec in total

First Response

530 ms

Resources Loaded

2.1 sec

Page Rendered

81 ms

original.rocks screenshot

About Website

Visit original.rocks now to see the best up-to-date Original content for Taiwan and also check out these interesting facts you probably never knew about original.rocks

設計自己的T-shirt, 幫你印, 幫你賣, 還幫你出貨! 還等甚麼! 這麼好康去哪裡找?

Visit original.rocks

Key Findings

We analyzed Original.rocks page load time and found that the first response time was 530 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

original.rocks performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

original.rocks

530 ms

yui_cssreset.css

247 ms

common.css

730 ms

jquery.min.js

1245 ms

originalrocks_logo.png

249 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that all of those requests were addressed to Original.rocks and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Original.rocks.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 kB (20%)

Content Size

8.6 kB

After Optimization

6.8 kB

In fact, the total size of Original.rocks main page is 8.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Images take 6.7 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 1.1 kB

  • Original 1.8 kB
  • After minification 1.6 kB
  • After compression 738 B

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. This page needs HTML code to be minified as it can gain 240 B, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.1 kB or 60% of the original size.

Image Optimization

-10%

Potential reduce by 648 B

  • Original 6.7 kB
  • After minification 6.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Original images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

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

Accessibility Review

original.rocks accessibility score

66

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

original.rocks best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

original.rocks SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Original.rocks can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Original.rocks 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 Original. 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: