Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

oracity.net

八戸市情報・オラシティ八戸 -青森県八戸市の地域検索-

Page Load Speed

11.4 sec in total

First Response

1.6 sec

Resources Loaded

9.4 sec

Page Rendered

441 ms

oracity.net screenshot

About Website

Click here to check amazing Oracity content for Japan. Otherwise, check out these important facts you probably never knew about oracity.net

青森県八戸市に特化した検索サイトです。会社やお店、不動産の検索、八戸フォーラム上映情報、八戸なんでも掲示板やグルメ情報掲示板など賑わっています。

Visit oracity.net

Key Findings

We analyzed Oracity.net page load time and found that the first response time was 1.6 sec and then it took 9.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

oracity.net performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

oracity.net

1561 ms

normalize.css

575 ms

common.css

773 ms

style.css

785 ms

jquery.bxslider.css

401 ms

Our browser made a total of 224 requests to load all elements on the main page. We found that 54% of them (122 requests) were addressed to the original Oracity.net, 11% (25 requests) were made to Static.xx.fbcdn.net and 9% (21 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Oracity.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 481.1 kB (14%)

Content Size

3.3 MB

After Optimization

2.9 MB

In fact, the total size of Oracity.net main page is 3.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 75.5 kB

  • Original 93.8 kB
  • After minification 86.6 kB
  • After compression 18.3 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 75.5 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 193.2 kB

  • Original 2.9 MB
  • After minification 2.7 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. Oracity images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 104.3 kB

  • Original 255.7 kB
  • After minification 223.9 kB
  • After compression 151.4 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 104.3 kB or 41% of the original size.

CSS Optimization

-88%

Potential reduce by 108.1 kB

  • Original 122.3 kB
  • After minification 102.8 kB
  • After compression 14.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. Oracity.net needs all CSS files to be minified and compressed as it can save up to 108.1 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

219

After Optimization

133

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

Accessibility Review

oracity.net accessibility score

82

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.

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

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

oracity.net best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

oracity.net SEO score

92

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

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

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