Tools & Wizards About Us
royaloc.cn screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

royaloc.cn

皇家海洋乐园 - 官方网站

Page Load Speed

7.5 sec in total

First Response

912 ms

Resources Loaded

6.4 sec

Page Rendered

178 ms

royaloc.cn screenshot

About Website

Welcome to royaloc.cn homepage info - get ready to check Royaloc best content right away, or after learning these important things about royaloc.cn

皇家海洋乐园,是亚洲最大的海洋馆,世界第一的极地海洋馆,亚洲最大室内沙滩冲浪馆,夏威夷沙滩冲浪馆,海洋馆及海洋科普,海洋动物,极地动物,世纪丛林,海兽城堡为一体的大型海洋娱乐科普基地

Visit royaloc.cn

Key Findings

We analyzed Royaloc.cn page load time and found that the first response time was 912 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

royaloc.cn performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.19

64/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

royaloc.cn

912 ms

AC_RunActiveContent.js

485 ms

jquery.lazyload.js

492 ms

jquery.js

744 ms

jquery.Slide.js

485 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 79% of them (74 requests) were addressed to the original Royaloc.cn, 13% (12 requests) were made to Tianqi.2345.com and 3% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Royaloc.cn.

Page Optimization Overview & Recommendations

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

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royaloc.cn main page is 1.8 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 34.3 kB

  • Original 42.9 kB
  • After minification 34.5 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 8.3 kB, which is 19% 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 34.3 kB or 80% of the original size.

Image Optimization

-18%

Potential reduce by 269.3 kB

  • Original 1.5 MB
  • After minification 1.3 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. Obviously, Royaloc needs image optimization as it can save up to 269.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 8.6 kB

  • Original 198.5 kB
  • After minification 198.5 kB
  • After compression 189.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 86 B

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 6.8 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. Royaloc.cn has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (45%)

Requests Now

91

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royaloc.cn

royaloc.cn

912 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

485 ms

jquery.lazyload.js

jquery.lazyload.js

492 ms

jquery.js

jquery.js

744 ms

jquery.Slide.js

jquery.Slide.js

485 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

489 ms

19515685.js

19515685.js

589 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

99 ms

bj.jpg

bj.jpg

1227 ms

kids.gif

kids.gif

248 ms

close.gif

close.gif

469 ms

%E5%88%86%E9%9A%94%E7%AC%A6.gif

%E5%88%86%E9%9A%94%E7%AC%A6.gif

477 ms

i_03.png

i_03.png

1229 ms

h2_04.png

h2_04.png

504 ms

h2_05.png

h2_05.png

711 ms

h2_06.png

h2_06.png

720 ms

h2_07.png

h2_07.png

733 ms

h2_08.png

h2_08.png

743 ms

h2_09.png

h2_09.png

952 ms

h2_10.png

h2_10.png

964 ms

h2_11.png

h2_11.png

978 ms

h2_12.png

h2_12.png

990 ms

h2_13.png

h2_13.png

1194 ms

h2_14.png

h2_14.png

1219 ms

h2_15.png

h2_15.png

1225 ms

h2_16.png

h2_16.png

1237 ms

h2_17.png

h2_17.png

1435 ms

h2_18.png

h2_18.png

1452 ms

h2_19.png

h2_19.png

1471 ms

h2_20.png

h2_20.png

1471 ms

h2_21.png

h2_21.png

1473 ms

h2_22.png

h2_22.png

1484 ms

h2_23.png

h2_23.png

1676 ms

h2_24.png

h2_24.png

1695 ms

i_09.png

i_09.png

1716 ms

i_12.png

i_12.png

1717 ms

but20170713_01.png

but20170713_01.png

1719 ms

but20170713_02.png

but20170713_02.png

1730 ms

111.png

111.png

1917 ms

but2018ykxz.png

but2018ykxz.png

1940 ms

index.htm

index.htm

520 ms

but20170713_05.png

but20170713_05.png

1740 ms

but20170713_06.png

but20170713_06.png

1736 ms

but20170713_07.png

but20170713_07.png

1735 ms

i_30.png

i_30.png

1695 ms

i_32.png

i_32.png

1712 ms

i_40.png

i_40.png

1709 ms

i_41.png

i_41.png

1702 ms

wea_plugin_widget.css

wea_plugin_widget.css

235 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

678 ms

common2_v20160923084755.js

common2_v20160923084755.js

471 ms

citySelectData.js

citySelectData.js

722 ms

interCitySelectData.js

interCitySelectData.js

970 ms

smallCityName.js

smallCityName.js

439 ms

widget.js

widget.js

456 ms

tianqiplugin

tianqiplugin

424 ms

i_42.png

i_42.png

1518 ms

eefc7903fa23a719978193702ab7a8f7.jpg

eefc7903fa23a719978193702ab7a8f7.jpg

2416 ms

6ecd148bff6d0cb7807c136e8c4fe279.jpg

6ecd148bff6d0cb7807c136e8c4fe279.jpg

2633 ms

04e8ee063172560dbfe077f218abb481.jpg

04e8ee063172560dbfe077f218abb481.jpg

2418 ms

h.js

h.js

686 ms

i_44.png

i_44.png

1505 ms

i_45.png

i_45.png

1495 ms

buy46_2.gif

buy46_2.gif

1497 ms

i_48.png

i_48.png

1713 ms

i_49.png

i_49.png

1512 ms

i_50.png

i_50.png

1506 ms

i_52.png

i_52.png

1723 ms

i_53.png

i_53.png

1726 ms

qq_01.png

qq_01.png

1746 ms

qq_02.png

qq_02.png

1957 ms

3.jpg

3.jpg

2007 ms

qq_04.png

qq_04.png

1768 ms

qq_05.png

qq_05.png

1910 ms

i_58.png

i_58.png

1932 ms

i_59.png

i_59.png

1968 ms

h.js

h.js

2188 ms

title6_01.png

title6_01.png

2230 ms

54353.js

54353.js

219 ms

54353.js

54353.js

223 ms

title6_02.png

title6_02.png

1930 ms

title6_03.png

title6_03.png

1934 ms

title6_06.png

title6_06.png

1931 ms

title6_04.png

title6_04.png

1991 ms

title6_05.png

title6_05.png

1990 ms

w_day.png

w_day.png

228 ms

plugin-widget.png

plugin-widget.png

223 ms

pd.png

pd.png

2119 ms

qq.png

qq.png

1957 ms

weixin.jpg

weixin.jpg

1952 ms

payi.png

payi.png

1970 ms

21.gif

21.gif

1607 ms

collect

collect

1475 ms

hm.gif

hm.gif

321 ms

Accessibility Review

royaloc.cn accessibility score

67

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

royaloc.cn 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

royaloc.cn SEO score

83

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

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royaloc.cn can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Royaloc.cn 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

royaloc.cn

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