Tools & Wizards About Us

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

solaripedia.com

Solaripedia | Green Architecture & Building | Solar Architecture and Green Building

Page Load Speed

1.2 sec in total

First Response

56 ms

Resources Loaded

1 sec

Page Rendered

134 ms

About Website

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

Solaripedia is a database of green architecture and green building resources using renewable solar, wind and passive strategies to create sustainable built environments.

Visit solaripedia.com

Key Findings

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

Performance Metrics

solaripedia.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value2,280 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

solaripedia.com

56 ms

www.solaripedia.com

189 ms

main.css

21 ms

thinbox.css

36 ms

dropdownmenu.js

34 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 71% of them (59 requests) were addressed to the original Solaripedia.com, 7% (6 requests) were made to Pagead2.googlesyndication.com and 5% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (321 ms) relates to the external source Top50-solar.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.4 kB (45%)

Content Size

658.4 kB

After Optimization

364.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Solaripedia.com main page is 658.4 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. 45% of websites need less resources to load. Javascripts take 358.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.4 kB

  • Original 23.6 kB
  • After minification 21.6 kB
  • After compression 6.2 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 17.4 kB or 74% of the original size.

Image Optimization

-25%

Potential reduce by 59.7 kB

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

JavaScript Optimization

-53%

Potential reduce by 190.6 kB

  • Original 358.1 kB
  • After minification 304.4 kB
  • After compression 167.4 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 190.6 kB or 53% of the original size.

CSS Optimization

-77%

Potential reduce by 26.8 kB

  • Original 34.5 kB
  • After minification 27.4 kB
  • After compression 7.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. Solaripedia.com needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

80

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

solaripedia.com accessibility score

56

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

solaripedia.com best practices score

67

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

solaripedia.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

Links are not crawlable

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

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Solaripedia.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Solaripedia.com 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

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