Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 68

    SEO

    Google-friendlier than
    27% of websites

osakazine.net

オオサカジン | 大阪の地域密着!登録無料のブログサービス

Page Load Speed

15.8 sec in total

First Response

892 ms

Resources Loaded

14.2 sec

Page Rendered

714 ms

osakazine.net screenshot

About Website

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

大阪市を中心とした地域ブログポータルサイトです。グルメ,観光,イベント,お店など、大阪の「イマ」を発信!

Visit osakazine.net

Key Findings

We analyzed Osakazine.net page load time and found that the first response time was 892 ms and then it took 14.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

osakazine.net performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.847

4/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

osakazine.net

892 ms

blog.osakazine.net

4565 ms

renewal20150311.css

653 ms

jquery.min.js

34 ms

top-osakaben.js

685 ms

Our browser made a total of 179 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Osakazine.net, 45% (81 requests) were made to Blog.osakazine.net and 25% (44 requests) were made to Img01.osakazine.net. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source Img01.osakazine.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.1 kB (6%)

Content Size

2.7 MB

After Optimization

2.6 MB

In fact, the total size of Osakazine.net main page is 2.7 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. 50% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 85.1 kB

  • Original 105.5 kB
  • After minification 93.0 kB
  • After compression 20.4 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 12.6 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 85.1 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 19.3 kB

  • Original 2.4 MB
  • After minification 2.4 MB

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. Osakazine images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 48.2 kB

  • Original 154.8 kB
  • After minification 152.9 kB
  • After compression 106.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 48.2 kB or 31% of the original size.

CSS Optimization

-82%

Potential reduce by 21.5 kB

  • Original 26.2 kB
  • After minification 19.5 kB
  • After compression 4.7 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. Osakazine.net needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

174

After Optimization

108

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

Accessibility Review

osakazine.net accessibility score

47

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>).

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

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

osakazine.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

osakazine.net SEO score

68

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

High

Page is blocked from indexing

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osakazine.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 Osakazine.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 Osakazine. 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: