Tools & Wizards About Us
publicdomainexplained.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

publicdomainexplained.com

Page Load Speed

2.2 sec in total

First Response

313 ms

Resources Loaded

903 ms

Page Rendered

952 ms

publicdomainexplained.com screenshot

About Website

Welcome to publicdomainexplained.com homepage info - get ready to check Publicdomainexplained best content right away, or after learning these important things about publicdomainexplained.com

Visit publicdomainexplained.com

Key Findings

We analyzed Publicdomainexplained.com page load time and found that the first response time was 313 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

publicdomainexplained.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.4 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.1 s

100/100

10%

Network Requests Diagram

publicdomainexplained.com

313 ms

flashobject.js

140 ms

3d_PDPG.jpg

402 ms

pde_bg.jpg

168 ms

pd_explained_graphics.jpg

283 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 211.4 kB (37%)

Content Size

573.6 kB

After Optimization

362.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-80%

Potential reduce by 49.4 kB

  • Original 61.4 kB
  • After minification 42.9 kB
  • After compression 12.0 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 18.5 kB, which is 30% 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 49.4 kB or 80% of the original size.

Image Optimization

-31%

Potential reduce by 157.7 kB

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

JavaScript Optimization

-70%

Potential reduce by 4.3 kB

  • Original 6.2 kB
  • After minification 5.7 kB
  • After compression 1.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 4.3 kB or 70% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • Images
  • JavaScript

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

Network Requests Diagram

publicdomainexplained.com

publicdomainexplained.com

313 ms

flashobject.js

flashobject.js

140 ms

3d_PDPG.jpg

3d_PDPG.jpg

402 ms

pde_bg.jpg

pde_bg.jpg

168 ms

pd_explained_graphics.jpg

pd_explained_graphics.jpg

283 ms

tony_sm.jpg

tony_sm.jpg

190 ms

icon-tick.gif

icon-tick.gif

148 ms

icon-arrow.gif

icon-arrow.gif

152 ms

stars1.jpg

stars1.jpg

208 ms

Mike_Sigers.jpg

Mike_Sigers.jpg

218 ms

CCs.jpg

CCs.jpg

279 ms

order.jpg

order.jpg

293 ms

movie.jpg

movie.jpg

319 ms

book.jpg

book.jpg

334 ms

audio.jpg

audio.jpg

347 ms

3d_PDPG.jpg

3d_PDPG.jpg

406 ms

PD_Outline1.jpg

PD_Outline1.jpg

345 ms

Periodical_Copyright_Resear.gif

Periodical_Copyright_Resear.gif

356 ms

checkbox.gif

checkbox.gif

381 ms

30-day_guarantee.jpg

30-day_guarantee.jpg

461 ms

table.jpg

table.jpg

394 ms

Accessibility Review

publicdomainexplained.com accessibility score

71

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

Document doesn't have a <title> element

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

Best Practices

publicdomainexplained.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

publicdomainexplained.com SEO score

50

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publicdomainexplained.com 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Publicdomainexplained.com 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

publicdomainexplained.com

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