Tools & Wizards About Us
atom.tools screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

atom.tools

ATOM | 業界シェアNo1！ネット広告・リスティング広告レポートを自動化、カスタマイズも自由自在

Page Load Speed

4.8 sec in total

First Response

327 ms

Resources Loaded

4.1 sec

Page Rendered

395 ms

atom.tools screenshot

About Website

Visit atom.tools now to see the best up-to-date ATOM content for Japan and also check out these interesting facts you probably never knew about atom.tools

リスティング広告、SNS広告、DSPなどの運用型広告データを集約し、広告レポート自動化と数値管理の簡略化を実現します。インターネット広告運用の工数削減と売上拡大を実現するWEB広告ツールです。

Visit atom.tools

Key Findings

We analyzed Atom.tools page load time and found that the first response time was 327 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

atom.tools performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

atom.tools

327 ms

www.atom.tools

684 ms

web_bootstrap.min.css

306 ms

font-awesome.min.css

449 ms

reset.css

448 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 64% of them (32 requests) were addressed to the original Atom.tools, 12% (6 requests) were made to Tag.brick.tools and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (957 ms) belongs to the original domain Atom.tools.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.2 kB (49%)

Content Size

534.5 kB

After Optimization

274.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Atom.tools main page is 534.5 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. 35% of websites need less resources to load. Images take 246.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.7 kB

  • Original 19.6 kB
  • After minification 14.3 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 27% 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 14.7 kB or 75% of the original size.

Image Optimization

-26%

Potential reduce by 63.0 kB

  • Original 246.0 kB
  • After minification 183.0 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, ATOM needs image optimization as it can save up to 63.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-35%

Potential reduce by 29.7 kB

  • Original 86.1 kB
  • After minification 86.1 kB
  • After compression 56.3 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 29.7 kB or 35% of the original size.

CSS Optimization

-83%

Potential reduce by 152.7 kB

  • Original 183.0 kB
  • After minification 169.2 kB
  • After compression 30.2 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. Atom.tools needs all CSS files to be minified and compressed as it can save up to 152.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (39%)

Requests Now

44

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

atom.tools

atom.tools

327 ms

www.atom.tools

www.atom.tools

684 ms

web_bootstrap.min.css

web_bootstrap.min.css

306 ms

font-awesome.min.css

font-awesome.min.css

449 ms

reset.css

reset.css

448 ms

webStyle.css

webStyle.css

453 ms

jquery.min.js

jquery.min.js

606 ms

bootstrap.min.js

bootstrap.min.js

462 ms

social.js

social.js

460 ms

css

css

62 ms

logo_web.png

logo_web.png

155 ms

main_img.png

main_img.png

307 ms

sec01_img01.png

sec01_img01.png

309 ms

sec01_img02.png

sec01_img02.png

153 ms

sec01_img03.png

sec01_img03.png

153 ms

sec02_img01.png

sec02_img01.png

169 ms

sec02_img02.png

sec02_img02.png

306 ms

api_google.png

api_google.png

449 ms

api_yahoo.png

api_yahoo.png

454 ms

api_facebook.png

api_facebook.png

324 ms

api_twitter.png

api_twitter.png

456 ms

api_criteo.png

api_criteo.png

600 ms

api_google-analytics-logo.png

api_google-analytics-logo.png

612 ms

sec03_img.png

sec03_img.png

473 ms

sec04_img.png

sec04_img.png

743 ms

img_tel_cvbox.png

img_tel_cvbox.png

605 ms

ft_fb.png

ft_fb.png

606 ms

ft_twitter.png

ft_twitter.png

623 ms

ft_contact.png

ft_contact.png

748 ms

gtm.js

gtm.js

164 ms

icon_link.png

icon_link.png

645 ms

icon_blankLink.png

icon_blankLink.png

646 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

957 ms

graph.facebook.com

graph.facebook.com

176 ms

google.php

google.php

838 ms

analytics.js

analytics.js

38 ms

conversion_async.js

conversion_async.js

63 ms

tag.js

tag.js

67 ms

brick.js

brick.js

83 ms

collect

collect

30 ms

tag

tag

47 ms

collect

collect

54 ms

UA-60580859-1.js

UA-60580859-1.js

670 ms

42 ms

ga-audiences

ga-audiences

25 ms

brick.company.js

brick.company.js

652 ms

brick.heatmap.js

brick.heatmap.js

10 ms

brick.lib.js

brick.lib.js

648 ms

check-landscape

check-landscape

855 ms

brick.heatmap_base.js

brick.heatmap_base.js

619 ms

Accessibility Review

atom.tools accessibility score

97

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

Links do not have a discernible name

Best Practices

atom.tools best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

atom.tools SEO score

90

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

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 Atom.tools 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 Atom.tools 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

atom.tools

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