Tools & Wizards About Us
project-future.org screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

project-future.org

Project Future - strip #55-02

Page Load Speed

3.8 sec in total

First Response

923 ms

Resources Loaded

2.6 sec

Page Rendered

286 ms

project-future.org screenshot

About Website

Welcome to project-future.org homepage info - get ready to check Project Future best content right away, or after learning these important things about project-future.org

Project Future - a sci-fi fantasy furry webcomic inspired by DMFA

Visit project-future.org

Key Findings

We analyzed Project-future.org page load time and found that the first response time was 923 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

project-future.org performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.554

13/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

project-future.org

923 ms

www.projectfuturecomic.com

419 ms

layout.css

64 ms

newsbox.js.php

597 ms

pf_logo.png

126 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Project-future.org, 76% (47 requests) were made to Projectfuturecomic.com and 23% (14 requests) were made to Xepher.net. The less responsive or slowest element that took the longest time to load (923 ms) belongs to the original domain Project-future.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.8 kB (2%)

Content Size

1.7 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Project-future.org main page is 1.7 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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 12.2 kB

  • Original 15.6 kB
  • After minification 12.8 kB
  • After compression 3.4 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 2.8 kB, which is 18% 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 12.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 15.0 kB

  • Original 1.6 MB
  • After minification 1.6 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. Project Future images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 11.5 kB

  • Original 47.8 kB
  • After minification 47.3 kB
  • After compression 36.3 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 11.5 kB or 24% of the original size.

CSS Optimization

-22%

Potential reduce by 47 B

  • Original 210 B
  • After minification 210 B
  • After compression 163 B

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. Project-future.org needs all CSS files to be minified and compressed as it can save up to 47 B or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (32%)

Requests Now

59

After Optimization

40

  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Project Future. 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 as a result speed up the page load time.

Network Requests Diagram

project-future.org

project-future.org

923 ms

www.projectfuturecomic.com

www.projectfuturecomic.com

419 ms

layout.css

layout.css

64 ms

newsbox.js.php

newsbox.js.php

597 ms

pf_logo.png

pf_logo.png

126 ms

pf_about.png

pf_about.png

164 ms

pf_cast.png

pf_cast.png

167 ms

pf_demo.png

pf_demo.png

190 ms

pf_forum.png

pf_forum.png

500 ms

pf_links.png

pf_links.png

594 ms

ep47-07.png

ep47-07.png

565 ms

pf_first.png

pf_first.png

226 ms

pf_rew.png

pf_rew.png

230 ms

pf_prev.png

pf_prev.png

253 ms

pf_archive.png

pf_archive.png

289 ms

pf_next2.png

pf_next2.png

292 ms

pf_ffwd2.png

pf_ffwd2.png

318 ms

pf_last.png

pf_last.png

353 ms

pfbanner300.png

pfbanner300.png

480 ms

xerianpanel.png

xerianpanel.png

446 ms

ernstpanel.png

ernstpanel.png

477 ms

bountypanel.png

bountypanel.png

575 ms

zetapanel.png

zetapanel.png

603 ms

sierrapanel.png

sierrapanel.png

543 ms

benpanel.png

benpanel.png

624 ms

shortspanel.png

shortspanel.png

671 ms

niallpanel.png

niallpanel.png

629 ms

simeonpanel8.png

simeonpanel8.png

650 ms

bfpanel.png

bfpanel.png

664 ms

DA_logo200.png

DA_logo200.png

668 ms

RVlogo200.png

RVlogo200.png

691 ms

azraelpanel.png

azraelpanel.png

691 ms

CMlogo200.png

CMlogo200.png

714 ms

axemanpanel.png

axemanpanel.png

791 ms

tuppennypanel.png

tuppennypanel.png

730 ms

daxxonpanel.png

daxxonpanel.png

734 ms

headspanel.png

headspanel.png

755 ms

darklordpanel.png

darklordpanel.png

754 ms

fishingpanel.png

fishingpanel.png

842 ms

pantherpanel.png

pantherpanel.png

737 ms

tenetspanel.png

tenetspanel.png

678 ms

harvestpanel.png

harvestpanel.png

660 ms

emilypanel.png

emilypanel.png

658 ms

Censor_14b.gif

Censor_14b.gif

673 ms

0.gif

0.gif

636 ms

3.gif

3.gif

636 ms

7.gif

7.gif

631 ms

1.gif

1.gif

601 ms

2.gif

2.gif

620 ms

newsbox.js.php

newsbox.js.php

293 ms

prototype.js

prototype.js

130 ms

scriptaculous.js

scriptaculous.js

196 ms

trans.gif

trans.gif

200 ms

XN-Dropdown.png

XN-Dropdown.png

199 ms

chevron-l.png

chevron-l.png

200 ms

chevron-r.png

chevron-r.png

245 ms

builder.js

builder.js

65 ms

effects.js

effects.js

71 ms

dragdrop.js

dragdrop.js

69 ms

controls.js

controls.js

74 ms

slider.js

slider.js

115 ms

XN-News-Background-Box.png

XN-News-Background-Box.png

66 ms

Accessibility Review

project-future.org accessibility score

87

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

Links do not have a discernible name

Best Practices

project-future.org 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

SEO Factors

project-future.org SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Project-future.org 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 Project-future.org main page’s claimed encoding is iso-8859-1. 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

project-future.org

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