Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

equj65.net

ギークを目指して

Page Load Speed

3.1 sec in total

First Response

576 ms

Resources Loaded

2.3 sec

Page Rendered

271 ms

equj65.net screenshot

About Website

Welcome to equj65.net homepage info - get ready to check Equj 65 best content for Japan right away, or after learning these important things about equj65.net

ギークになりたくてもなれないギーク志望エンジニアの技術blog。日々の技術ネタを紹介していきます。

Visit equj65.net

Key Findings

We analyzed Equj65.net page load time and found that the first response time was 576 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

equj65.net performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

equj65.net

576 ms

c073d00e867e9c7c703e8535d2a711de.css

293 ms

default.min.css

304 ms

shCore.css

313 ms

shCoreEmacs.css

334 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 41% of them (18 requests) were addressed to the original Equj65.net, 18% (8 requests) were made to Apis.google.com and 7% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (934 ms) belongs to the original domain Equj65.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.4 kB (48%)

Content Size

398.9 kB

After Optimization

206.5 kB

In fact, the total size of Equj65.net main page is 398.9 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 192.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 33.3 kB

  • Original 40.2 kB
  • After minification 36.4 kB
  • After compression 6.9 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 33.3 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 968 B

  • Original 111.3 kB
  • After minification 110.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. Equj 65 images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 115.0 kB

  • Original 192.4 kB
  • After minification 183.0 kB
  • After compression 77.4 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 115.0 kB or 60% of the original size.

CSS Optimization

-78%

Potential reduce by 43.2 kB

  • Original 55.1 kB
  • After minification 49.6 kB
  • After compression 11.9 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. Equj65.net needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (48%)

Requests Now

42

After Optimization

22

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Equj 65. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

equj65.net accessibility score

52

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Low

No form fields have multiple labels

High

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

High

Form elements do not have associated labels

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

equj65.net best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

equj65.net SEO score

99

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

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