Tools & Wizards About Us
wellshadow.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wellshadow.com

PetroCode - Wellbore Diagram Software, Well Diagrams

Page Load Speed

3.1 sec in total

First Response

47 ms

Resources Loaded

2.8 sec

Page Rendered

293 ms

wellshadow.com screenshot

About Website

Click here to check amazing Well Shadow content. Otherwise, check out these important facts you probably never knew about wellshadow.com

Well Shadow is an application designed to make creating wellbore diagrams and well histories quick and easy. It is no longer necessary to use Microsoft Excel to create cumbersome wellbore diagrams.

Visit wellshadow.com

Key Findings

We analyzed Wellshadow.com page load time and found that the first response time was 47 ms and then it took 3.1 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

wellshadow.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value2,080 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

wellshadow.com

47 ms

www.petrocode.com

197 ms

www.petrocode.com

725 ms

scripts.js

322 ms

js

99 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wellshadow.com, 42% (50 requests) were made to Dev.seedtechnologies.com and 29% (34 requests) were made to Petrocode.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Petrocode.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.2 kB (5%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 32.1 kB

  • Original 42.5 kB
  • After minification 40.5 kB
  • After compression 10.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. 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 32.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 752.0 kB
  • After minification 752.0 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. Well Shadow images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.1 kB

  • Original 223.0 kB
  • After minification 222.8 kB
  • After compression 218.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. This website has mostly compressed JavaScripts.

CSS Optimization

-36%

Potential reduce by 23.0 kB

  • Original 63.5 kB
  • After minification 63.0 kB
  • After compression 40.5 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. Wellshadow.com needs all CSS files to be minified and compressed as it can save up to 23.0 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (76%)

Requests Now

100

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wellshadow.com

wellshadow.com

47 ms

www.petrocode.com

www.petrocode.com

197 ms

www.petrocode.com

www.petrocode.com

725 ms

scripts.js

scripts.js

322 ms

js

js

99 ms

js

js

163 ms

modernizr

modernizr

51 ms

stem-menu.css

stem-menu.css

121 ms

icon

icon

70 ms

jquery

jquery

91 ms

survey.jquery.min.js

survey.jquery.min.js

195 ms

css

css

179 ms

font-awesome.min.css

font-awesome.min.css

120 ms

codemirror.min.css

codemirror.min.css

130 ms

froala_editor.pkgd.min.css

froala_editor.pkgd.min.css

95 ms

styles.css

styles.css

316 ms

stem-member.css

stem-member.css

314 ms

stem-member-directory.css

stem-member-directory.css

313 ms

stem-search-input.css

stem-search-input.css

714 ms

api.js

api.js

84 ms

events.css

events.css

313 ms

CurrentEventShortCode.css

CurrentEventShortCode.css

313 ms

seed.catalogSideMenu.css

seed.catalogSideMenu.css

314 ms

seed.clearanceProducts.css

seed.clearanceProducts.css

321 ms

seed.popularProducts.css

seed.popularProducts.css

747 ms

seed

seed

323 ms

jqueryval

jqueryval

321 ms

moment

moment

323 ms

jquery@3.7.1

jquery@3.7.1

51 ms

jquery.js

jquery.js

39 ms

request-additional-information

request-additional-information

845 ms

PetroCodeLogo.r1pou4fgbfv21lsy.png

PetroCodeLogo.r1pou4fgbfv21lsy.png

85 ms

searchIconWhite.2ncypsjb3rgetrhk.png

searchIconWhite.2ncypsjb3rgetrhk.png

84 ms

verticalSample.9etc8m0boyvtbswj.jpg

verticalSample.9etc8m0boyvtbswj.jpg

1117 ms

horizontalSample1.qz442g7m9u1m5r4p.jpg

horizontalSample1.qz442g7m9u1m5r4p.jpg

178 ms

horizontalSample2.c1r45d3r38oyu92q.jpg

horizontalSample2.c1r45d3r38oyu92q.jpg

185 ms

freeTrialMonitor.4joz82r12ppfsjqk.png

freeTrialMonitor.4joz82r12ppfsjqk.png

232 ms

tutorialMonitorOnly.8jkgpsgdjjx7el32.png

tutorialMonitorOnly.8jkgpsgdjjx7el32.png

268 ms

phoneCTA.75nvnz4xo5z32m4f.png

phoneCTA.75nvnz4xo5z32m4f.png

278 ms

facebookSquare.oy3hjvclkmqu758u.jpg

facebookSquare.oy3hjvclkmqu758u.jpg

322 ms

twitterSquare.3lbyvg6nu4i9lzyr.jpg

twitterSquare.3lbyvg6nu4i9lzyr.jpg

329 ms

youtubeSquare.0v0qftjtmooe98gh.jpg

youtubeSquare.0v0qftjtmooe98gh.jpg

368 ms

recaptcha__en.js

recaptcha__en.js

29 ms

reset.css

reset.css

71 ms

architecture.css

architecture.css

71 ms

header-ex1.css

header-ex1.css

78 ms

header-ex2.css

header-ex2.css

79 ms

header-ex3.css

header-ex3.css

116 ms

header-ex4.css

header-ex4.css

117 ms

header-ex5.css

header-ex5.css

156 ms

header-ex6.css

header-ex6.css

157 ms

header-ex7.css

header-ex7.css

162 ms

header-ex8.css

header-ex8.css

163 ms

header-ex9.css

header-ex9.css

163 ms

clientHeader-ex1.css

clientHeader-ex1.css

166 ms

clientHeader-ex2.css

clientHeader-ex2.css

194 ms

bannerBar-ex1.css

bannerBar-ex1.css

193 ms

socialBar-ex1.css

socialBar-ex1.css

198 ms

socialBar-ex2.css

socialBar-ex2.css

199 ms

socialBar-ex3.css

socialBar-ex3.css

200 ms

menuBar-ex1.css

menuBar-ex1.css

201 ms

footer-ex1.css

footer-ex1.css

230 ms

footer-ex2.css

footer-ex2.css

231 ms

footer-ex3.css

footer-ex3.css

235 ms

footer-ex4.css

footer-ex4.css

235 ms

footer-ex5.css

footer-ex5.css

236 ms

footer-ex6.css

footer-ex6.css

238 ms

banner-ex1.css

banner-ex1.css

266 ms

banner-ex2.css

banner-ex2.css

268 ms

rotatingBanner.css

rotatingBanner.css

289 ms

smlbanner-ex1.css

smlbanner-ex1.css

272 ms

cookies.css

cookies.css

272 ms

titles.css

titles.css

275 ms

testimonials.css

testimonials.css

304 ms

copyright.css

copyright.css

305 ms

socialBars.css

socialBars.css

308 ms

CTA-ex1.css

CTA-ex1.css

310 ms

CTA.css

CTA.css

313 ms

panels.css

panels.css

332 ms

css

css

19 ms

accordian-ex1.css

accordian-ex1.css

277 ms

contactForm-ex1.css

contactForm-ex1.css

276 ms

contactForm-ex2.css

contactForm-ex2.css

272 ms

rotator-ex1.css

rotator-ex1.css

271 ms

snap-carousel-ex1.css

snap-carousel-ex1.css

238 ms

gallery.css

gallery.css

256 ms

clientIcon.yqdxs4ul2ndlmjul.png

clientIcon.yqdxs4ul2ndlmjul.png

119 ms

clockIcon.5o3r01o9orb0tfb6.png

clockIcon.5o3r01o9orb0tfb6.png

567 ms

banner1-alt.y2wzvmm9cjh9pkkt.jpg

banner1-alt.y2wzvmm9cjh9pkkt.jpg

147 ms

freeeTrialBG.6kwxd2mm7la42i20.jpg

freeeTrialBG.6kwxd2mm7la42i20.jpg

639 ms

45daysCorner.kf4kmdng2hfvlfjg.png

45daysCorner.kf4kmdng2hfvlfjg.png

1067 ms

-W__XJnvUD7dzB2KYNoY.ttf

-W__XJnvUD7dzB2KYNoY.ttf

81 ms

-W_8XJnvUD7dzB2Ck_kIaWMr.ttf

-W_8XJnvUD7dzB2Ck_kIaWMr.ttf

87 ms

-W_8XJnvUD7dzB2Cy_gIaWMr.ttf

-W_8XJnvUD7dzB2Cy_gIaWMr.ttf

90 ms

-W_8XJnvUD7dzB2Cr_sIaWMr.ttf

-W_8XJnvUD7dzB2Cr_sIaWMr.ttf

90 ms

-W_8XJnvUD7dzB2Cx_wIaWMr.ttf

-W_8XJnvUD7dzB2Cx_wIaWMr.ttf

91 ms

scripts.js

scripts.js

71 ms

scripts.js

scripts.js

51 ms

scripts.js

scripts.js

51 ms

scripts.js

scripts.js

51 ms

snap-carousel-ex1.js

snap-carousel-ex1.js

51 ms

fallback

fallback

77 ms

-W_6XJnvUD7dzB2KZeK4aFMsW5U.ttf

-W_6XJnvUD7dzB2KZeK4aFMsW5U.ttf

20 ms

-W_6XJnvUD7dzB2KZeLsbVMsW5U.ttf

-W_6XJnvUD7dzB2KZeLsbVMsW5U.ttf

16 ms

-W_9XJnvUD7dzB2KZeofTkM.ttf

-W_9XJnvUD7dzB2KZeofTkM.ttf

21 ms

-W_6XJnvUD7dzB2KZeK0bFMsW5U.ttf

-W_6XJnvUD7dzB2KZeK0bFMsW5U.ttf

32 ms

-W_6XJnvUD7dzB2KZeLQb1MsW5U.ttf

-W_6XJnvUD7dzB2KZeLQb1MsW5U.ttf

31 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

18 ms

logo_48.png

logo_48.png

3 ms

seed

seed

57 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

5 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

6 ms

scripts.js

scripts.js

40 ms

fallback

fallback

34 ms

fallback

fallback

80 ms

fallback

fallback

2 ms

fallback

fallback

25 ms

Accessibility Review

wellshadow.com accessibility score

81

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

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

High

Form elements do not have associated labels

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

wellshadow.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wellshadow.com SEO score

100

Search Engine Optimization Advices

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

wellshadow.com

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