2.1 sec in total
91 ms
1.3 sec
682 ms
Welcome to sjfss.com homepage info - get ready to check Sjfss best content right away, or after learning these important things about sjfss.com
Welcome to the official website of the 4th Force Support Squadron at Seymour Johnson AFB, North Carolina! Visit us often to find out what’s going on around base and how you can be a part of it.
Visit sjfss.comWe analyzed Sjfss.com page load time and found that the first response time was 91 ms and then it took 2 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.
sjfss.com performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value9.0 s
1/100
25%
Value5.4 s
56/100
10%
Value1,060 ms
25/100
30%
Value0.007
100/100
15%
Value9.0 s
33/100
10%
91 ms
206 ms
72 ms
74 ms
81 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 94% of them (126 requests) were addressed to the original Sjfss.com, 4% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (312 ms) belongs to the original domain Sjfss.com.
Page size can be reduced by 716.2 kB (24%)
3.0 MB
2.3 MB
In fact, the total size of Sjfss.com main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 683.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 683.4 kB or 86% of the original size.
Potential reduce by 32.8 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. Sjfss images are well optimized though.
Potential reduce by 12 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.
Number of requests can be reduced by 109 (89%)
123
14
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sjfss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 69 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
sjfss.com
91 ms
sjfss.com
206 ms
accessibility.min.css
72 ms
tribe-events-full.min.css
74 ms
tribe-events-pro-full.min.css
81 ms
jquery-ui-1.8.23.custom.css
82 ms
bootstrap-datepicker.standalone.min.css
79 ms
tribe-events-theme.min.css
88 ms
events-single.min.css
94 ms
tribe-events-pro-mini-calendar-block.min.css
98 ms
dashicons.min.css
127 ms
variables-skeleton.min.css
102 ms
variables-full.min.css
102 ms
common-skeleton.min.css
112 ms
common-full.min.css
120 ms
tickets.min.css
122 ms
rsvp-v1.min.css
127 ms
tickets.min.css
130 ms
general.css
135 ms
style.css
143 ms
app.min.css
144 ms
rsvp.min.css
149 ms
style-static.min.css
210 ms
style.css
155 ms
responsive.css
160 ms
main.css
165 ms
main-media-query.css
168 ms
animations.css
174 ms
jquery.min.js
206 ms
jquery-migrate.min.js
184 ms
php-date-formatter.min.js
189 ms
css
41 ms
scripts.js
173 ms
scripts.js
180 ms
scripts.js
236 ms
scripts.js
236 ms
popper-1.16.1.min.js
237 ms
tippy-5.2.1.min.js
237 ms
viewer.js
109 ms
style.css
201 ms
tooltipster.bundle.min.css
198 ms
views-skeleton.min.css
195 ms
views-skeleton.min.css
190 ms
views-full.min.css
191 ms
views-full.min.css
189 ms
style.css
198 ms
events-virtual-skeleton.min.css
193 ms
events-virtual-full.min.css
189 ms
archives.min.css
185 ms
gdpr-cookie-consent-public.min.css
185 ms
tribe-common.min.js
172 ms
attendees-list.min.js
172 ms
events-dynamic.min.js
169 ms
rsvp.min.js
171 ms
ticket-details.min.js
178 ms
jquery.deparam.js
174 ms
jquery.cookie.js
170 ms
meta.min.js
166 ms
scripts.min.js
312 ms
hooks.min.js
158 ms
i18n.min.js
163 ms
app.min.js
295 ms
frontend-bundle.min.js
294 ms
main.js
289 ms
common.js
274 ms
custom.js
272 ms
core.min.js
266 ms
mouse.min.js
259 ms
draggable.min.js
212 ms
jquery.nanoscroller.min.js
210 ms
week-grid-scroller.min.js
211 ms
accordion.min.js
210 ms
week-day-selector.min.js
207 ms
week-multiday-toggle.min.js
205 ms
week-event-link.min.js
206 ms
map-events-scroller.min.js
206 ms
swiper.min.js
206 ms
map-no-venue-modal.min.js
204 ms
map-provider-google-maps.min.js
192 ms
map-events.min.js
190 ms
tooltipster.bundle.min.js
191 ms
tooltip.min.js
190 ms
tooltip-pro.min.js
190 ms
multiday-events.min.js
190 ms
multiday-events-pro.min.js
185 ms
toggle-recurrence.min.js
184 ms
bootstrap-datepicker.min.js
182 ms
datepicker.min.js
182 ms
app.js
169 ms
datepicker-pro.min.js
171 ms
query-string.min.js
168 ms
underscore-before.js
168 ms
underscore.min.js
166 ms
underscore-after.js
167 ms
manager.min.js
165 ms
breakpoints.min.js
27 ms
viewport.min.js
27 ms
view-selector.min.js
25 ms
ical-links.min.js
24 ms
navigation-scroll.min.js
27 ms
month-mobile-events.min.js
27 ms
month-grid.min.js
48 ms
events-bar.min.js
47 ms
events-bar-inputs.min.js
46 ms
bootstrap.bundle.js
111 ms
gdpr-cookie-consent-public.min.js
50 ms
jquery.fitvids.js
47 ms
jquery.mobile.js
117 ms
lazyload.min.js
184 ms
Seymour-Johnson-logo.png
114 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
158 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
159 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
159 ms
fa-solid-900.woff
119 ms
fa-brands-400.woff
156 ms
fa-regular-400.woff
117 ms
modules.woff
118 ms
web_Bunco-copy.gif
148 ms
Plane-Sept-13.png
223 ms
HeartsApart-web.gif
199 ms
stv_Meet-Your-Key-Support-Liaison.jpg
169 ms
stv_PickleballTournament-new-date.png
175 ms
web_AFBdayBash-copy.gif
175 ms
cac-card-1-4a63d669.webp
167 ms
1200x250_web-banner-copy-0200fc11.webp
177 ms
blank-d3ad7009.webp
188 ms
logo-ice.png
198 ms
Air-Force-Services.png
199 ms
tribe-events-full-mobile.min.css
26 ms
tribe-events-theme-mobile.min.css
26 ms
views-print.min.css
26 ms
views-print.min.css
25 ms
sjfss.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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sjfss.com 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
sjfss.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Sjfss.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 Sjfss.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.
sjfss.com
Open Graph description is not detected on the main page of Sjfss. 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: