3.3 sec in total
258 ms
2.9 sec
150 ms
Welcome to ezproxy.csusm.edu homepage info - get ready to check Ezproxy Csusm best content for United States right away, or after learning these important things about ezproxy.csusm.edu
Visit ezproxy.csusm.eduWe analyzed Ezproxy.csusm.edu page load time and found that the first response time was 258 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.
ezproxy.csusm.edu performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.2 s
44/100
25%
Value6.4 s
40/100
10%
Value150 ms
94/100
30%
Value0.157
74/100
15%
Value5.7 s
68/100
10%
258 ms
162 ms
709 ms
50 ms
34 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ezproxy.csusm.edu, 27% (23 requests) were made to Biblio.csusm.edu and 23% (19 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (903 ms) relates to the external source Lib.csusm.edu.
Page size can be reduced by 680.5 kB (40%)
1.7 MB
1.0 MB
In fact, the total size of Ezproxy.csusm.edu main page is 1.7 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. 65% of websites need less resources to load. Images take 788.1 kB which makes up the majority of the site volume.
Potential reduce by 58.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 58.0 kB or 75% of the original size.
Potential reduce by 8.3 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. Ezproxy Csusm images are well optimized though.
Potential reduce by 341.7 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 341.7 kB or 70% of the original size.
Potential reduce by 272.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. Ezproxy.csusm.edu needs all CSS files to be minified and compressed as it can save up to 272.5 kB or 82% of the original size.
Number of requests can be reduced by 46 (61%)
75
29
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezproxy Csusm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
ezproxy.csusm.edu
258 ms
login
162 ms
ezproxylogin
709 ms
api.js
50 ms
font-awesome.min.css
34 ms
css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css
273 ms
css_hRsjYoHDDNWSCY3dBO3XP3tTCGHZ_wh7XElu_DgPy8w.css
273 ms
css_Ny-TdZlNncmgsDWGlbCfYkGFEw9A3eQ85geA-F6tZnw.css
354 ms
css_B9xFcNyDC9H57eJPC2oPBI3ZGX6exhQhH1VPf6ABuII.css
274 ms
bootstrap.min.css
43 ms
css_T7396LHcH1fPCqlnV3Pcn1PCUm_FU3b8U9NfUcPEZcQ.css
276 ms
recaptcha__en.js
82 ms
css
129 ms
css_OdU8Nu_KR6TbRnaAsxuDjv5v3GFcsZXY5olDKSwtZvg.css
288 ms
yamm.css
290 ms
dataTables.bootstrap.min.css
105 ms
frontpage.css
381 ms
jquery-1.10.2.min.js
97 ms
jquery-migrate-1.2.1.min.js
96 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
297 ms
jquery-ui.min.js
104 ms
js_KCd8rbJYUruV1tRJnh4um34UYvyhlrSVCPR1jNko2h8.js
329 ms
bootstrap.min.js
23 ms
js_pnabiwnHCcvRO4JUkEF4BIW0oRO0P50QKALzAORglF8.js
364 ms
js_pfyVuGKJN8oA4kxsL9nVgrVG3CdRHm1oz3zRqxBDWS8.js
367 ms
js_QsRZLiZ1Xzl17OChfFp1DVpdsJbs5mIhadMeuvbagvE.js
376 ms
js_j1KVRCceH5sVld6kpzxiZx0paPt0NLBl4FQG2Iopm0k.js
437 ms
jquery.cookie.min.js
97 ms
scripts.js
441 ms
responsive-tabs.js
444 ms
jquery.dataTables.min.js
46 ms
dataTables.bootstrap.min.js
13 ms
js_29qYXJz8NLGg8Aomg-RZPjJcj9yEdEst1BMZ9gZbs-4.js
385 ms
analytics.js
169 ms
librarylogo-4-med_0.png
127 ms
ask-librarian2.png
232 ms
sprite-main1.png
117 ms
fontawesome-webfont.woff
19 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
40 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
41 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
40 ms
index.php
666 ms
widgets.js
81 ms
piwik.js
903 ms
aVWFkTP0RX1td3s4ev4bCQ.js
78 ms
fallback
93 ms
extlink_s.png
93 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
13 ms
syndication
106 ms
499054709835976705
187 ms
collect
48 ms
fallback__ltr.css
7 ms
payload
27 ms
css
19 ms
logo_48.png
6 ms
refresh.png
6 ms
audio.png
9 ms
CdzOZ9WUAAATOq0.jpg
47 ms
1f426.png
100 ms
CdrvnDbXIAAyopq.jpg
88 ms
CdhyoefXIAA5bk9.jpg
88 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
14 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
36 ms
I2_ZaYzO_normal.jpg
65 ms
dtqnl9w04pyn0cw7jk8k_normal.jpeg
72 ms
FlRjF4DL_normal.png
70 ms
ZRu-6gol_normal.jpg
69 ms
3d8PYmSD_normal.jpg
72 ms
CdTcW1lUkAAYfet.jpg
88 ms
CdNPBEuUkAAsfoV.jpg
72 ms
CdD2uJwVAAUAs7d.jpg
165 ms
CdCloPYUEAEdKAn.jpg
87 ms
Cc_L3RJUEAA4ylv.jpg
90 ms
Cc-h5QQUUAAYnOH.jpg:large
88 ms
CcvcJT8VAAAahBY.jpg
89 ms
CcqcFo2UkAAyftO.jpg
90 ms
Cco-dTKUsAET_0j.jpg
90 ms
CckTfKpVAAAsowe.jpg
97 ms
CcgRYfnUcAAvVBW.jpg
91 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
4 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
11 ms
jot
25 ms
icon_close.png
62 ms
index.php
174 ms
ezproxy.csusm.edu accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ezproxy.csusm.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ezproxy.csusm.edu SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Ezproxy.csusm.edu 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 Ezproxy.csusm.edu 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.
ezproxy.csusm.edu
Open Graph description is not detected on the main page of Ezproxy Csusm. 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: