Tools & Wizards About Us
t-q.co.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

t-q.co.jp

日本橋の貸事務所【トップクォーター株式会社】 | トップクォーター株式会社

Page Load Speed

3.9 sec in total

First Response

1.2 sec

Resources Loaded

2.6 sec

Page Rendered

124 ms

t-q.co.jp screenshot

About Website

Welcome to t-q.co.jp homepage info - get ready to check T Q best content right away, or after learning these important things about t-q.co.jp

日本橋の貸事務所・貸ビルはオフィス専門のトップクォーターにお任せください！主に、中央区、他にも、渋谷区や新宿区、豊島区の事業用賃貸を豊富に取り扱っております。是非、お問い合わせください。

Visit t-q.co.jp

Key Findings

We analyzed T-q.co.jp page load time and found that the first response time was 1.2 sec and then it took 2.7 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

t-q.co.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value16.6 s

0/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.492

17/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

t-q.co.jp

1189 ms

style.css

587 ms

comscript.js

398 ms

main.pl

435 ms

tq1.jpg

230 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 96% of them (22 requests) were addressed to the original T-q.co.jp, 4% (1 request) were made to 0. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain T-q.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.7 kB (43%)

Content Size

86.8 kB

After Optimization

49.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of T-q.co.jp main page is 86.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. Only 5% of websites need less resources to load. Images take 38.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.0 kB

  • Original 35.9 kB
  • After minification 35.9 kB
  • After compression 8.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 27.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 152 B

  • Original 38.1 kB
  • After minification 37.9 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. T Q images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 4.0 kB

  • Original 4.9 kB
  • After minification 3.8 kB
  • After compression 881 B

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 4.0 kB or 82% of the original size.

CSS Optimization

-83%

Potential reduce by 6.6 kB

  • Original 7.9 kB
  • After minification 6.5 kB
  • After compression 1.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. T-q.co.jp needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

22

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

t-q.co.jp

t-q.co.jp

1189 ms

style.css

style.css

587 ms

comscript.js

comscript.js

398 ms

main.pl

main.pl

435 ms

tq1.jpg

tq1.jpg

230 ms

tqlogo.gif

tqlogo.gif

213 ms

bot01.gif

bot01.gif

270 ms

bot02.gif

bot02.gif

384 ms

bot03.gif

bot03.gif

391 ms

bot04.gif

bot04.gif

432 ms

tq2.jpg

tq2.jpg

643 ms

tq3.jpg

tq3.jpg

440 ms

tq4.gif

tq4.gif

471 ms

step1.gif

step1.gif

566 ms

map.gif

map.gif

769 ms

kensaku.gif

kensaku.gif

646 ms

step2.gif

step2.gif

645 ms

step3.gif

step3.gif

693 ms

step4.gif

step4.gif

774 ms

tq5.gif

tq5.gif

835 ms

ensen.gif

ensen.gif

857 ms

kensaku02.gif

kensaku02.gif

848 ms

tqfooter.jpg

tqfooter.jpg

1103 ms

Accessibility Review

t-q.co.jp accessibility score

66

Accessibility Issues

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

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

t-q.co.jp best practices score

75

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

SEO Factors

t-q.co.jp SEO score

70

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 T-q.co.jp 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 T-q.co.jp 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

t-q.co.jp

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