Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

Page Load Speed

2.9 sec in total

First Response

380 ms

Resources Loaded

2 sec

Page Rendered

515 ms

johnty.idv.st screenshot

About Website

Click here to check amazing Johnty Idv content for Taiwan. Otherwise, check out these important facts you probably never knew about johnty.idv.st

Visit johnty.idv.st

Key Findings

We analyzed Johnty.idv.st page load time and found that the first response time was 380 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

johnty.idv.st performance score

0

Network Requests Diagram

johnty.idv.st

380 ms

oneoftenmeteo

42 ms

bar.htm

71 ms

geocities

42 ms

banner_igame_1035x76.jpg

1327 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Johnty.idv.st, 17% (16 requests) were made to Sep.yimg.com and 9% (8 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Img.i-gamer.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 284.3 kB (30%)

Content Size

939.8 kB

After Optimization

655.5 kB

In fact, the total size of Johnty.idv.st main page is 939.8 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. Images take 668.4 kB which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 399 B

  • Original 813 B
  • After minification 744 B
  • After compression 414 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. 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 399 B or 49% of the original size.

Image Optimization

-22%

Potential reduce by 145.8 kB

  • Original 668.4 kB
  • After minification 522.6 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, Johnty Idv needs image optimization as it can save up to 145.8 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 33.2 kB

  • Original 142.6 kB
  • After minification 142.6 kB
  • After compression 109.5 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 33.2 kB or 23% of the original size.

CSS Optimization

-82%

Potential reduce by 104.9 kB

  • Original 127.9 kB
  • After minification 127.9 kB
  • After compression 23.0 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. Johnty.idv.st needs all CSS files to be minified and compressed as it can save up to 104.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (64%)

Requests Now

78

After Optimization

28

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

Accessibility Review

johnty.idv.st accessibility score

33

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

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

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

Best Practices

johnty.idv.st best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

johnty.idv.st SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnty.idv.st 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Johnty.idv.st main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Johnty Idv. 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: