Tools & Wizards About Us
catch-e.net screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

catch-e.net

[キャッチー]：茨城県つくば市のホームページ制作会社

Page Load Speed

3.4 sec in total

First Response

902 ms

Resources Loaded

2.5 sec

Page Rendered

83 ms

catch-e.net screenshot

About Website

Welcome to catch-e.net homepage info - get ready to check Catch E best content right away, or after learning these important things about catch-e.net

茨城県つくば市のwebサイト・システム制作業。ホームページから始める中小企業向け広告戦略とITシステム支援。

Visit catch-e.net

Key Findings

We analyzed Catch-e.net page load time and found that the first response time was 902 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

catch-e.net performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

catch-e.net

902 ms

style.css

174 ms

logic.js

340 ms

js

70 ms

analytics.js

91 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 89% of them (31 requests) were addressed to the original Catch-e.net, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (902 ms) belongs to the original domain Catch-e.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.6 kB (14%)

Content Size

52.8 kB

After Optimization

45.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Catch-e.net main page is 52.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. 15% of websites need less resources to load. Javascripts take 21.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.2 kB

  • Original 10.4 kB
  • After minification 9.1 kB
  • After compression 3.3 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. This page needs HTML code to be minified as it can gain 1.4 kB, 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 7.2 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 19.5 kB
  • After minification 19.5 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. Catch E images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 160 B

  • Original 21.8 kB
  • After minification 21.8 kB
  • After compression 21.6 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.

CSS Optimization

-22%

Potential reduce by 234 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 850 B

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. Catch-e.net needs all CSS files to be minified and compressed as it can save up to 234 B or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

34

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

catch-e.net

catch-e.net

902 ms

style.css

style.css

174 ms

logic.js

logic.js

340 ms

js

js

70 ms

analytics.js

analytics.js

91 ms

ta_01.jpg

ta_01.jpg

343 ms

sw_03.gif

sw_03.gif

173 ms

sw_01.gif

sw_01.gif

333 ms

sw_02.gif

sw_02.gif

347 ms

mail.gif

mail.gif

382 ms

header_01.gif

header_01.gif

381 ms

header_02.gif

header_02.gif

382 ms

menu_u_01.gif

menu_u_01.gif

499 ms

menu_u_02.gif

menu_u_02.gif

516 ms

menu_u_03.gif

menu_u_03.gif

518 ms

menu_u_04.gif

menu_u_04.gif

574 ms

menu_u_05.gif

menu_u_05.gif

574 ms

menu_u_06.gif

menu_u_06.gif

575 ms

menu_u_07.gif

menu_u_07.gif

666 ms

menu_u_08.gif

menu_u_08.gif

689 ms

menu_u_09.gif

menu_u_09.gif

695 ms

adst.gif

adst.gif

765 ms

header_03.gif

header_03.gif

766 ms

tab.gif

tab.gif

766 ms

footer_05.gif

footer_05.gif

832 ms

footer_000.gif

footer_000.gif

869 ms

collect

collect

29 ms

js

js

47 ms

menu_o_02.gif

menu_o_02.gif

175 ms

menu_o_03.gif

menu_o_03.gif

178 ms

menu_o_04.gif

menu_o_04.gif

195 ms

menu_o_05.gif

menu_o_05.gif

168 ms

menu_o_06.gif

menu_o_06.gif

193 ms

menu_o_08.gif

menu_o_08.gif

193 ms

menu_o_09.gif

menu_o_09.gif

334 ms

Accessibility Review

catch-e.net accessibility score

93

Accessibility Issues

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

catch-e.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

catch-e.net SEO score

69

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catch-e.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Catch-e.net 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

catch-e.net

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