Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

Page Load Speed

5.7 sec in total

First Response

1.5 sec

Resources Loaded

4.1 sec

Page Rendered

110 ms

sun.worldcat.org screenshot

About Website

Visit sun.worldcat.org now to see the best up-to-date Sun Worldcat content for United States and also check out these interesting facts you probably never knew about sun.worldcat.org

Visit sun.worldcat.org

Key Findings

We analyzed Sun.worldcat.org page load time and found that the first response time was 1.5 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

sun.worldcat.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

sun.worldcat.org

1524 ms

modals_jquery.css

26 ms

jquery.min.js

8 ms

jquery-ui.min.js

12 ms

autocomplete.js

24 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 10% of them (3 requests) were addressed to the original Sun.worldcat.org, 71% (22 requests) were made to Static1.worldcat.org and 10% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn.sabinet.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.4 kB (31%)

Content Size

88.7 kB

After Optimization

61.3 kB

In fact, the total size of Sun.worldcat.org main page is 88.7 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. 40% of websites need less resources to load. Javascripts take 33.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.9 kB

  • Original 33.2 kB
  • After minification 30.0 kB
  • After compression 8.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 24.9 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 2.5 kB

  • Original 21.6 kB
  • After minification 19.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. Obviously, Sun Worldcat needs image optimization as it can save up to 2.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 15 B

  • Original 33.8 kB
  • After minification 33.8 kB
  • After compression 33.8 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.

Requests Breakdown

Number of requests can be reduced by 24 (80%)

Requests Now

30

After Optimization

6

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

Accessibility Review

sun.worldcat.org accessibility score

100

Accessibility Issues

Best Practices

sun.worldcat.org 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

High

Missing source maps for large first-party JavaScript

SEO Factors

sun.worldcat.org SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sun.worldcat.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Sun.worldcat.org 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 Sun Worldcat. 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: