Tools & Wizards About Us
smart-c.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

smart-c.jp

アフィリエイト Smart-C（スマートシー）

Page Load Speed

5.4 sec in total

First Response

332 ms

Resources Loaded

4.5 sec

Page Rendered

548 ms

smart-c.jp screenshot

About Website

Click here to check amazing Smart C content for Japan. Otherwise, check out these important facts you probably never knew about smart-c.jp

アフィリエイトサービス『Smart-C(スマートシー)』は、国内最大級のスマートフォン向け広告配信サービスです。多数のメディア様と広告主様にご利用いただいており、メディア様の広告収益最大化と広告主様の目的に応じた効果的なプロモーションをサポートいたします。

Visit smart-c.jp

Key Findings

We analyzed Smart-c.jp page load time and found that the first response time was 332 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

smart-c.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

smart-c.jp

332 ms

smart-c.jp

690 ms

gtm.js

55 ms

reset.min.css

486 ms

style.css

806 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 87% of them (27 requests) were addressed to the original Smart-c.jp, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Smart-c.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.9 kB (17%)

Content Size

1.1 MB

After Optimization

890.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smart-c.jp main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 853.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.4 kB

  • Original 15.1 kB
  • After minification 13.3 kB
  • After compression 4.7 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.8 kB, which is 12% 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 10.4 kB or 69% of the original size.

Image Optimization

-5%

Potential reduce by 40.7 kB

  • Original 853.6 kB
  • After minification 812.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. Smart C images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 92.3 kB

  • Original 158.6 kB
  • After minification 152.7 kB
  • After compression 66.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 92.3 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 33.4 kB

  • Original 39.6 kB
  • After minification 30.8 kB
  • After compression 6.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. Smart-c.jp needs all CSS files to be minified and compressed as it can save up to 33.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (38%)

Requests Now

29

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smart-c.jp

smart-c.jp

332 ms

smart-c.jp

smart-c.jp

690 ms

gtm.js

gtm.js

55 ms

reset.min.css

reset.min.css

486 ms

style.css

style.css

806 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

968 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

648 ms

analysis.js

analysis.js

487 ms

jquery.loader.js

jquery.loader.js

486 ms

jquery.smoothScroll.js

jquery.smoothScroll.js

1126 ms

inView.js

inView.js

1050 ms

fixedNavi.js

fixedNavi.js

1049 ms

modal.js

modal.js

1211 ms

cssua.min.js

cssua.min.js

1287 ms

js

js

43 ms

ga.js

ga.js

82 ms

page_bg.jpg

page_bg.jpg

952 ms

smartc_logo_animation_white.png

smartc_logo_animation_white.png

1515 ms

smartc_logo.svg

smartc_logo.svg

539 ms

smartc_logo_white.svg

smartc_logo_white.svg

614 ms

fv_phone.png

fv_phone.png

1833 ms

line.svg

line.svg

780 ms

maximization.png

maximization.png

1361 ms

simple.png

simple.png

1274 ms

n_insentive.png

n_insentive.png

1445 ms

insentive.png

insentive.png

1615 ms

roi.png

roi.png

1934 ms

security.png

security.png

2027 ms

jask_logo.png

jask_logo.png

2101 ms

Teko-Regular.woff

Teko-Regular.woff

2440 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

smart-c.jp accessibility score

91

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.

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

smart-c.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

smart-c.jp SEO score

92

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

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

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 Smart-c.jp 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 Smart-c.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

smart-c.jp

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