Tools & Wizards About Us
138files.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

138files.com

一宮市地域情報サイト ★ 138FILES（いちのみやふぁいるず）

Page Load Speed

9.7 sec in total

First Response

1.2 sec

Resources Loaded

8.4 sec

Page Rendered

177 ms

138files.com screenshot

About Website

Click here to check amazing 138FILES content. Otherwise, check out these important facts you probably never knew about 138files.com

一宮市の地域サイトです。一宮市限定の検索エンジン、メールマガジン、メーリングリスト、その他各種コミュニティ

Visit 138files.com

Key Findings

We analyzed 138files.com page load time and found that the first response time was 1.2 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

138files.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

138files.com

1165 ms

basestyle.css

717 ms

urchin.js

7 ms

show_ads.js

7 ms

ad.js

8 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 67% of them (28 requests) were addressed to the original 138files.com, 10% (4 requests) were made to Pagead2.googlesyndication.com and 7% (3 requests) were made to A248.e.akamai.net. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain 138files.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.5 kB (46%)

Content Size

169.8 kB

After Optimization

92.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 138files.com main page is 169.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. 25% of websites need less resources to load. Javascripts take 58.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 36.0 kB

  • Original 47.5 kB
  • After minification 45.8 kB
  • After compression 11.5 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 36.0 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 4.3 kB

  • Original 56.3 kB
  • After minification 52.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. 138FILES images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 30.7 kB

  • Original 58.4 kB
  • After minification 48.6 kB
  • After compression 27.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 30.7 kB or 53% of the original size.

CSS Optimization

-85%

Potential reduce by 6.5 kB

  • Original 7.6 kB
  • After minification 6.6 kB
  • After compression 1.1 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. 138files.com needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (46%)

Requests Now

41

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

138files.com

138files.com

1165 ms

basestyle.css

basestyle.css

717 ms

urchin.js

urchin.js

7 ms

show_ads.js

show_ads.js

7 ms

ad.js

ad.js

8 ms

__utm.gif

__utm.gif

36 ms

100.gif

100.gif

6605 ms

banner.jpg

banner.jpg

6596 ms

138toplogo2.png

138toplogo2.png

6594 ms

mmm.jpg

mmm.jpg

6599 ms

new2.gif

new2.gif

6595 ms

go2rx20.gif

go2rx20.gif

6595 ms

list1.gif

list1.gif

6596 ms

ya1.gif

ya1.gif

6596 ms

list2.gif

list2.gif

6596 ms

list3.gif

list3.gif

6598 ms

dummy.gif

dummy.gif

6598 ms

go2rx16.gif

go2rx16.gif

6599 ms

w10.gif

w10.gif

6599 ms

m1.gif

m1.gif

6600 ms

m2.gif

m2.gif

6601 ms

aoki4.jpg

aoki4.jpg

6601 ms

hioki01.jpg

hioki01.jpg

6606 ms

mmmchina.png

mmmchina.png

6606 ms

list0.gif

list0.gif

6601 ms

t-files09.gif

t-files09.gif

6604 ms

f-file02.gif

f-file02.gif

6602 ms

fuji_bn1.gif

fuji_bn1.gif

6601 ms

138Files.gif

138Files.gif

6602 ms

a-files02.gif

a-files02.gif

6603 ms

wc_ss.gif

wc_ss.gif

6604 ms

g-narupara.gif

g-narupara.gif

6608 ms

kabosu.gif

kabosu.gif

6606 ms

futaba.gif

futaba.gif

6606 ms

ad1.js

ad1.js

2 ms

format_468x120.js

format_468x120.js

6557 ms

ca-pub-4142918112069361.js

ca-pub-4142918112069361.js

103 ms

zrt_lookup.html

zrt_lookup.html

100 ms

show_ads_impl.js

show_ads_impl.js

63 ms

ads

ads

85 ms

osd.js

osd.js

5 ms

ad

ad

363 ms

Accessibility Review

138files.com accessibility score

48

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

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

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

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

138files.com 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

138files.com SEO score

69

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 138files.com 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 138files.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

138files.com

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