Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

zenzibar.com

Zenzibar

Page Load Speed

512 ms in total

First Response

101 ms

Resources Loaded

258 ms

Page Rendered

153 ms

zenzibar.com screenshot

About Website

Welcome to zenzibar.com homepage info - get ready to check Zenzibar best content for United States right away, or after learning these important things about zenzibar.com

Zenzibar is the personal website of Royce Carlson and Juanita Hull-Carlson.

Visit zenzibar.com

Key Findings

We analyzed Zenzibar.com page load time and found that the first response time was 101 ms and then it took 411 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

zenzibar.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

zenzibar.com

101 ms

Zenlogopale.gif

34 ms

zenheader11.jpg

129 ms

cosmicsteel-bw.jpg

129 ms

creativeconcretebw.jpg

110 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that all of those requests were addressed to Zenzibar.com and no external sources were called. The less responsive or slowest element that took the longest time to load (153 ms) belongs to the original domain Zenzibar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.4 kB (26%)

Content Size

473.2 kB

After Optimization

351.8 kB

In fact, the total size of Zenzibar.com main page is 473.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 469.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 2.6 kB

  • Original 3.6 kB
  • After minification 3.0 kB
  • After compression 990 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. This page needs HTML code to be minified as it can gain 676 B, 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 2.6 kB or 73% of the original size.

Image Optimization

-25%

Potential reduce by 118.8 kB

  • Original 469.6 kB
  • After minification 350.8 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, Zenzibar needs image optimization as it can save up to 118.8 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zenzibar. According to our analytics all requests are already optimized.

Accessibility Review

zenzibar.com accessibility score

54

Accessibility Issues

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

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

SEO Factors

zenzibar.com SEO score

62

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zenzibar.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 Zenzibar.com main page’s claimed encoding is windows-1252. 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

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