2.1 sec in total
321 ms
1.4 sec
415 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 321 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.7 s
29/100
10%
Value8.6 s
1/100
25%
Value5.3 s
58/100
10%
Value410 ms
67/100
30%
Value0.02
100/100
15%
Value9.4 s
31/100
10%
321 ms
42 ms
28 ms
74 ms
161 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Catchmark.com, 42% (21 requests) were made to Pchassets.blob.core.windows.net and 8% (4 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (667 ms) relates to the external source Pchassets.blob.core.windows.net.
Page size can be reduced by 214.1 kB (21%)
1.0 MB
793.7 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. 45% of websites need less resources to load. Images take 879.3 kB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 22% 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 35.4 kB or 81% 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 635 B
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.
Potential reduce by 15.2 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 15.2 kB or 35% of the original size.
Number of requests can be reduced by 19 (42%)
45
26
The browser has sent 45 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 7 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.potlatchdeltic.com
321 ms
js
42 ms
bootstrap.min.css
28 ms
site.min.css
74 ms
fontsMobile.css
161 ms
fontsDesktop.css
210 ms
fontsMax.css
270 ms
headerMobile.css
279 ms
headerDesktop.css
278 ms
headerMax.css
291 ms
header.js
323 ms
templateOneMobile.css
323 ms
templateOneDesktop.css
337 ms
templateOneMax.css
342 ms
templateOne.js
363 ms
footerMobile.css
367 ms
footerDesktop.css
371 ms
footerMax.css
373 ms
jquery-2.2.0.min.js
32 ms
bootstrap.min.js
32 ms
js
41 ms
PotlatchDeltic-Logo.png
283 ms
navArrow.png
175 ms
Arrow-Button.png
175 ms
icon-investors.png
307 ms
icon-login.png
316 ms
icon-search.png
308 ms
home-support-1_@1.jpg
373 ms
Ark265-375x180.jpg
539 ms
icon-timberlands.png
350 ms
icon-lumber.png
377 ms
NewREiconFINALhighrez.png
448 ms
home-hunting-1_@1.jpg
526 ms
istock82552-375x180.jpg
556 ms
home-support-2_@1.jpg
443 ms
IdahoForest326-375x180.jpg
595 ms
ESGHub.png
523 ms
OurApproach.png
528 ms
CarbonClimate.png
592 ms
home-support-3_@1.jpg
595 ms
IdahoForest149375x180.jpg
667 ms
Spotlight.png
615 ms
icon-hiring.png
624 ms
Community.png
663 ms
ai.2.min.js
21 ms
GetStockQuoteList
60 ms
roboto-medium-webfont.woff
73 ms
roboto-black-webfont.woff
136 ms
roboto-light-webfont.woff
148 ms
glyphicons-halflings-regular.woff
3 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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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
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
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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: