Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ocg.xpg.tw

AsiaCards

Page Load Speed

6.8 sec in total

First Response

1.5 sec

Resources Loaded

5.3 sec

Page Rendered

91 ms

ocg.xpg.tw screenshot

About Website

Visit ocg.xpg.tw now to see the best up-to-date Ocg Xpg content for Taiwan and also check out these interesting facts you probably never knew about ocg.xpg.tw

最完整的遊戲王卡牌查詢網站

Visit ocg.xpg.tw

Key Findings

We analyzed Ocg.xpg.tw page load time and found that the first response time was 1.5 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ocg.xpg.tw performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

ocg.xpg.tw

1497 ms

main.css

1105 ms

jquery-latest.min.js

7 ms

jquery.easing.1.3.js

763 ms

hyperlink2.js

718 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 27% of them (12 requests) were addressed to the original Ocg.xpg.tw, 18% (8 requests) were made to Apis.google.com and 7% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Ocg.xpg.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.1 kB (57%)

Content Size

641.3 kB

After Optimization

274.3 kB

In fact, the total size of Ocg.xpg.tw main page is 641.3 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. 50% of websites need less resources to load. Javascripts take 447.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 51.7 kB

  • Original 75.4 kB
  • After minification 74.4 kB
  • After compression 23.8 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 51.7 kB or 69% of the original size.

Image Optimization

-21%

Potential reduce by 22.1 kB

  • Original 104.4 kB
  • After minification 82.3 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. Obviously, Ocg Xpg needs image optimization as it can save up to 22.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 281.4 kB

  • Original 447.3 kB
  • After minification 439.8 kB
  • After compression 165.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 281.4 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 11.9 kB

  • Original 14.3 kB
  • After minification 10.6 kB
  • After compression 2.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Ocg.xpg.tw needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (58%)

Requests Now

40

After Optimization

17

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ocg Xpg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

ocg.xpg.tw accessibility score

75

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

ocg.xpg.tw 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

ocg.xpg.tw SEO score

92

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

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

    N/A

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ocg.xpg.tw can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Ocg.xpg.tw 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 Ocg Xpg. 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: