Tools & Wizards About Us
solterra.us screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

solterra.us

SolTerra | Web design, graphic design, and video production in Ohio and Kentucky.

Page Load Speed

1.2 sec in total

First Response

119 ms

Resources Loaded

673 ms

Page Rendered

399 ms

solterra.us screenshot

About Website

Click here to check amazing Sol Terra content. Otherwise, check out these important facts you probably never knew about solterra.us

SolTerra provides web design, graphic design and video production services. We put our best creative talents toward any size project. Contact us for a free consultation.

Visit solterra.us

Key Findings

We analyzed Solterra.us page load time and found that the first response time was 119 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

solterra.us performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

solterra.us

119 ms

solterra.us

195 ms

css

35 ms

75818.js

177 ms

plusone.js

30 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 18% of them (7 requests) were addressed to the original Solterra.us, 49% (19 requests) were made to Solterra-website-bucket.s3.amazonaws.com and 13% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (319 ms) relates to the external source Solterra-website-bucket.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.3 kB (4%)

Content Size

7.3 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Solterra.us main page is 7.3 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 7.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.6 kB

  • Original 25.2 kB
  • After minification 23.6 kB
  • After compression 5.6 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 19.6 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 300.5 kB

  • Original 7.2 MB
  • After minification 6.9 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. Sol Terra images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 3.3 kB

  • Original 103.4 kB
  • After minification 102.3 kB
  • After compression 100.2 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 12 (38%)

Requests Now

32

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

solterra.us

solterra.us

119 ms

solterra.us

solterra.us

195 ms

css

css

35 ms

75818.js

75818.js

177 ms

plusone.js

plusone.js

30 ms

fbevents.js

fbevents.js

112 ms

fewliveasync.js

fewliveasync.js

139 ms

ga.js

ga.js

75 ms

web_hover.png

web_hover.png

184 ms

LargeWhiteLogo.png

LargeWhiteLogo.png

200 ms

video_hover.png

video_hover.png

178 ms

print_hover.png

print_hover.png

182 ms

about_hover.png

about_hover.png

178 ms

web_hoverMobile.gif

web_hoverMobile.gif

134 ms

video_hoverMobile.gif

video_hoverMobile.gif

175 ms

print_hoverMobile.gif

print_hoverMobile.gif

175 ms

about_hoverMobile.gif

about_hoverMobile.gif

277 ms

OhioRiverSunset.jpg

OhioRiverSunset.jpg

205 ms

big.png

big.png

246 ms

web.png

web.png

249 ms

video.png

video.png

242 ms

print.png

print.png

252 ms

about.png

about.png

312 ms

blue-background.png

blue-background.png

292 ms

SolTerraLogoWhite.png

SolTerraLogoWhite.png

286 ms

envelope_contact_white.png

envelope_contact_white.png

318 ms

facebook-icon.png

facebook-icon.png

319 ms

GooglePlus-logo-1.png

GooglePlus-logo-1.png

315 ms

facebook-icon_white.png

facebook-icon_white.png

173 ms

GooglePlus-logo_white.png

GooglePlus-logo_white.png

171 ms

twitter-icon_white.png

twitter-icon_white.png

171 ms

twitter-icon.png

twitter-icon.png

171 ms

__utm.gif

__utm.gif

39 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

43 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

62 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

65 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

68 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

70 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

Accessibility Review

solterra.us accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

solterra.us 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

solterra.us SEO score

92

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

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Solterra.us 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 Solterra.us 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

solterra.us

Open Graph data is detected on the main page of Sol Terra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: