1.8 sec in total
22 ms
1.4 sec
349 ms
Click here to check amazing Catchmark content. Otherwise, check out these important facts you probably never knew about catchmark.com
Visit catchmark.comWe analyzed Catchmark.com page load time and found that the first response time was 22 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
catchmark.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.7 s
1/100
25%
Value5.1 s
61/100
10%
Value140 ms
95/100
30%
Value0.002
100/100
15%
Value8.3 s
39/100
10%
22 ms
28 ms
360 ms
48 ms
25 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Catchmark.com, 43% (22 requests) were made to Potlatchdeltic.com and 41% (21 requests) were made to Pchassets.blob.core.windows.net. The less responsive or slowest element that took the longest time to load (715 ms) relates to the external source Pchassets.blob.core.windows.net.
Page size can be reduced by 228.0 kB (22%)
1.0 MB
793.1 kB
In fact, the total size of Catchmark.com main page is 1.0 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. 40% of websites need less resources to load. Images take 879.3 kB which makes up the majority of the site volume.
Potential reduce by 39.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. This page needs HTML code to be minified as it can gain 10.8 kB, which is 23% 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 39.0 kB or 82% of the original size.
Potential reduce by 162.9 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, Catchmark needs image optimization as it can save up to 162.9 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.0 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 9.0 kB or 18% of the original size.
Potential reduce by 17.1 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. Catchmark.com needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 39% of the original size.
Number of requests can be reduced by 18 (42%)
43
25
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Catchmark. 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 from 14 to 1 for CSS and as a result speed up the page load time.
catchmark.com
22 ms
potlatchdeltic.com
28 ms
www.potlatchdeltic.com
360 ms
js
48 ms
bootstrap.min.css
25 ms
site.min.css
85 ms
fontsMobile.css
163 ms
fontsDesktop.css
240 ms
fontsMax.css
302 ms
headerMobile.css
295 ms
headerDesktop.css
310 ms
headerMax.css
319 ms
header.js
323 ms
templateOneMobile.css
327 ms
templateOneDesktop.css
389 ms
templateOneMax.css
390 ms
templateOne.js
400 ms
footerMobile.css
400 ms
footerDesktop.css
400 ms
footerMax.css
405 ms
jquery-2.2.0.min.js
29 ms
bootstrap.min.js
27 ms
PotlatchDeltic-Logo.png
353 ms
navArrow.png
178 ms
Arrow-Button.png
178 ms
icon-investors.png
323 ms
icon-login.png
327 ms
icon-search.png
325 ms
home-support-1_@1.jpg
393 ms
Ark265-375x180.jpg
537 ms
icon-timberlands.png
395 ms
icon-lumber.png
397 ms
NewREiconFINALhighrez.png
485 ms
home-hunting-1_@1.jpg
559 ms
istock82552-375x180.jpg
609 ms
home-support-2_@1.jpg
540 ms
IdahoForest326-375x180.jpg
613 ms
ESGHub.png
570 ms
OurApproach.png
622 ms
CarbonClimate.png
638 ms
home-support-3_@1.jpg
632 ms
IdahoForest149375x180.jpg
715 ms
Spotlight.png
685 ms
icon-hiring.png
686 ms
Community.png
697 ms
ai.2.min.js
56 ms
roboto-medium-webfont.woff
92 ms
roboto-black-webfont.woff
161 ms
roboto-light-webfont.woff
149 ms
glyphicons-halflings-regular.woff
8 ms
GetStockQuoteList
33 ms
catchmark.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
catchmark.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
catchmark.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catchmark.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 Catchmark.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.
catchmark.com
Open Graph description is not detected on the main page of Catchmark. 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: