Tools & Wizards About Us
pgg-eng.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pgg-eng.com

Peterson Geotechnical Group – Peterson Geotechnical Group

Page Load Speed

2.8 sec in total

First Response

711 ms

Resources Loaded

1.9 sec

Page Rendered

170 ms

pgg-eng.com screenshot

About Website

Click here to check amazing Pgg Eng content. Otherwise, check out these important facts you probably never knew about pgg-eng.com

Peterson Geotechnical Group specializes in forensic geotechnical evaluations for slab cracks, foundation settlement and movement. We service New Mexico, Arizona and throughout the Southwest.

Visit pgg-eng.com

Key Findings

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

Performance Metrics

pgg-eng.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

www.pgg-eng.com

711 ms

wp-emoji-release.min.js

58 ms

156-layout.css

107 ms

styles.css

112 ms

font-awesome.min.css

117 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 82% of them (36 requests) were addressed to the original Pgg-eng.com, 5% (2 requests) were made to Smartslider3.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (711 ms) belongs to the original domain Pgg-eng.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.3 kB (3%)

Content Size

3.8 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pgg-eng.com main page is 3.8 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. 45% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 43.2 kB

  • Original 56.2 kB
  • After minification 55.4 kB
  • After compression 13.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. 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 43.2 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 53.6 kB

  • Original 3.5 MB
  • After minification 3.5 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. Pgg Eng images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 3.9 kB

  • Original 144.8 kB
  • After minification 144.8 kB
  • After compression 140.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

-13%

Potential reduce by 4.6 kB

  • Original 36.5 kB
  • After minification 36.5 kB
  • After compression 31.9 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. Pgg-eng.com needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pgg-eng.com

www.pgg-eng.com

711 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

58 ms

156-layout.css

156-layout.css

107 ms

styles.css

styles.css

112 ms

font-awesome.min.css

font-awesome.min.css

117 ms

bootstrap-front.css

bootstrap-front.css

109 ms

animate.css

animate.css

111 ms

bb-header-footer.css

bb-header-footer.css

115 ms

style.css

style.css

218 ms

font-awesome.min.css

font-awesome.min.css

34 ms

mobilenav.css

mobilenav.css

166 ms

style.min.css

style.min.css

165 ms

smartslider.min.css

smartslider.min.css

170 ms

jquery.js

jquery.js

231 ms

jquery-migrate.min.js

jquery-migrate.min.js

180 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

224 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

224 ms

jquery.theme-main.min.js

jquery.theme-main.min.js

225 ms

mobilenav.min.js

mobilenav.min.js

247 ms

n2.min.js

n2.min.js

272 ms

nextend-frontend.min.js

nextend-frontend.min.js

333 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

347 ms

smartslider-simple-type-frontend.min.js

smartslider-simple-type-frontend.min.js

278 ms

nextend-webfontloader.min.js

nextend-webfontloader.min.js

286 ms

so-css-vantage.css

so-css-vantage.css

288 ms

156-layout.js

156-layout.js

318 ms

scripts.js

scripts.js

336 ms

bootstrap.js

bootstrap.js

345 ms

bb-header-footer.js

bb-header-footer.js

344 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

372 ms

wp-embed.min.js

wp-embed.min.js

451 ms

css

css

31 ms

programmer.jpg

programmer.jpg

118 ms

free1.jpg

free1.jpg

136 ms

P1010156.jpg

P1010156.jpg

272 ms

DSC00037.jpg

DSC00037.jpg

320 ms

Concrete-Crack.jpg

Concrete-Crack.jpg

308 ms

foundation-problem.jpg

foundation-problem.jpg

163 ms

IMG_3363.jpg

IMG_3363.jpg

321 ms

vantage-icons.woff

vantage-icons.woff

57 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

38 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

46 ms

programmer.jpg

programmer.jpg

37 ms

free1.jpg

free1.jpg

17 ms

Accessibility Review

pgg-eng.com accessibility score

96

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

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

pgg-eng.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

pgg-eng.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 Pgg-eng.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 Pgg-eng.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

pgg-eng.com

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