1.4 sec in total
337 ms
895 ms
188 ms
Click here to check amazing Saa content for United States. Otherwise, check out these important facts you probably never knew about saa.org
The SAA is an international organization dedicated to the research, interpretation, and protection of the archaeological heritage of the Americas.
Visit saa.orgWe analyzed Saa.org page load time and found that the first response time was 337 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.
saa.org performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value7.6 s
4/100
25%
Value3.9 s
83/100
10%
Value350 ms
73/100
30%
Value0.179
67/100
15%
Value6.6 s
57/100
10%
337 ms
180 ms
169 ms
118 ms
86 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original Saa.org, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to D1ev1rt26nhnwq.cloudfront.net. The less responsive or slowest element that took the longest time to load (524 ms) belongs to the original domain Saa.org.
Page size can be reduced by 540.8 kB (44%)
1.2 MB
687.5 kB
In fact, the total size of Saa.org main page is 1.2 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. 25% of websites need less resources to load. Images take 611.2 kB which makes up the majority of the site volume.
Potential reduce by 146.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 146.4 kB or 90% of the original size.
Potential reduce by 39.1 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. Saa images are well optimized though.
Potential reduce by 302.3 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 302.3 kB or 77% of the original size.
Potential reduce by 53.0 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. Saa.org needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 89% of the original size.
Number of requests can be reduced by 21 (55%)
38
17
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
saa.org
337 ms
module.css
180 ms
default.css
169 ms
skin.css
118 ms
portal.css
86 ms
WebResource.axd
81 ms
WebResource.axd
168 ms
dnncore.js
169 ms
spmenu.js
236 ms
dnn.js
208 ms
ScriptResource.axd
248 ms
ScriptResource.axd
206 ms
ScriptResource.axd
209 ms
ScriptResource.axd
210 ms
ScriptResource.axd
247 ms
ScriptResource.axd
261 ms
analytics.js
32 ms
ccmtblv2.png
54 ms
bg.jpg
99 ms
spacer.gif
99 ms
Advances_webs.jpg
217 ms
facebook_32x32.png
135 ms
twitter_32x32.png
164 ms
linkedin_32x32.png
141 ms
ConfIntLogo_ForHomepage_RGB_TanBox.png
171 ms
min.gif
178 ms
SAA_OSS_Logo_RGB_webSmall.jpg
196 ms
action_print.gif
214 ms
Jan2012cover.png
274 ms
AQ77(1)covers-1.png
298 ms
LAQ20(3).jpg
402 ms
SAAJournal_Advances_Web343x119_R1.jpg
400 ms
CRO.jpg
524 ms
SAAPress_Button.jpg
388 ms
collect
24 ms
header.jpg
326 ms
navbg.gif
304 ms
spacer.gif
348 ms
nav_space.gif
349 ms
saa.org accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
saa.org 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
Issues were logged in the Issues panel in Chrome Devtools
saa.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Saa.org 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 Saa.org 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.
saa.org
Open Graph description is not detected on the main page of Saa. 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: