Tools & Wizards About Us
my180.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

my180.com

Orion180 Portal

Page Load Speed

26.7 sec in total

First Response

878 ms

Resources Loaded

25.6 sec

Page Rendered

255 ms

my180.com screenshot

About Website

Click here to check amazing My 180 content for Japan. Otherwise, check out these important facts you probably never knew about my180.com

Manage your homeowners insurance policy

Visit my180.com

Key Findings

We analyzed My180.com page load time and found that the first response time was 878 ms and then it took 25.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 13 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

my180.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

my180.com

878 ms

u_12604.html

1392 ms

global.css

760 ms

123logo.gif

5918 ms

db380x60.gif

3888 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original My180.com, 52% (28 requests) were made to 5w123.com and 28% (15 requests) were made to Yeuss.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source 5w123.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.1 kB (18%)

Content Size

402.2 kB

After Optimization

330.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of My180.com main page is 402.2 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. 15% of websites need less resources to load. Images take 323.0 kB which makes up the majority of the site volume.

HTML Optimization

-19%

Potential reduce by 67 B

  • Original 362 B
  • After minification 360 B
  • After compression 295 B

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 67 B or 19% of the original size.

Image Optimization

-5%

Potential reduce by 14.9 kB

  • Original 323.0 kB
  • After minification 308.2 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. My 180 images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 40.8 kB

  • Original 57.9 kB
  • After minification 50.3 kB
  • After compression 17.1 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 40.8 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 16.4 kB

  • Original 20.9 kB
  • After minification 18.2 kB
  • After compression 4.5 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. My180.com needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (33%)

Requests Now

39

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

my180.com

my180.com

878 ms

u_12604.html

u_12604.html

1392 ms

global.css

global.css

760 ms

123logo.gif

123logo.gif

5918 ms

db380x60.gif

db380x60.gif

3888 ms

360buy.gif

360buy.gif

520 ms

db100x60.jpg

db100x60.jpg

2469 ms

baidu.gif

baidu.gif

5407 ms

1453709533.jpg

1453709533.jpg

16579 ms

1453709571.jpg

1453709571.jpg

11369 ms

1453709595.jpg

1453709595.jpg

16512 ms

1452500244.jpg

1452500244.jpg

5999 ms

1453710102.jpg

1453710102.jpg

20440 ms

1453710121.jpg

1453710121.jpg

18498 ms

1453710139.jpg

1453710139.jpg

7511 ms

123tu5.js

123tu5.js

506 ms

stat.php

stat.php

1145 ms

c.js

c.js

326 ms

1453710157.jpg

1453710157.jpg

9301 ms

1453710176.jpg

1453710176.jpg

12032 ms

1452849949.jpg

1452849949.jpg

20435 ms

1452849967.jpg

1452849967.jpg

14042 ms

1452849986.jpg

1452849986.jpg

15808 ms

1452850004.jpg

1452850004.jpg

17586 ms

1452850022.jpg

1452850022.jpg

20435 ms

1452494762.jpg

1452494762.jpg

20434 ms

1452494779.jpg

1452494779.jpg

19383 ms

1452494797.jpg

1452494797.jpg

20434 ms

1452494817.jpg

1452494817.jpg

20435 ms

1452494839.jpg

1452494839.jpg

20435 ms

1446717118.jpg

1446717118.jpg

20435 ms

1446717136.jpg

1446717136.jpg

20434 ms

1446717156.jpg

1446717156.jpg

20435 ms

1446717173.jpg

1446717173.jpg

20435 ms

1447162224.jpg

1447162224.jpg

20434 ms

topbg.jpg

topbg.jpg

255 ms

images.gif

images.gif

254 ms

searchbg.jpg

searchbg.jpg

256 ms

searchbg.gif

searchbg.gif

493 ms

btnbg.gif

btnbg.gif

518 ms

specrecom_20110927.png

specrecom_20110927.png

517 ms

tmall.png

tmall.png

516 ms

jd.png

jd.png

518 ms

qn.gif

qn.gif

518 ms

index_icon.gif

index_icon.gif

758 ms

sale5.png

sale5.png

20172 ms

stat.htm

stat.htm

285 ms

core.php

core.php

786 ms

9.gif

9.gif

810 ms

h.js

h.js

2608 ms

app.gif

app.gif

930 ms

hm.gif

hm.gif

1283 ms

sed_api_weather_info.php

sed_api_weather_info.php

2841 ms

hm.gif

hm.gif

924 ms

Accessibility Review

my180.com accessibility score

93

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

Image elements do not have [alt] attributes

Best Practices

my180.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

my180.com SEO score

85

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

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 uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My180.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 My180.com main page’s claimed encoding is gb2312. 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

my180.com

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