5.1 sec in total
264 ms
4.1 sec
677 ms
Click here to check amazing Spf content for Spain. Otherwise, check out these important facts you probably never knew about spf.com
Discover our new Spring / Summer collection | Shop the Women's and Men's latest fashion at our online store | Springfield
Visit spf.comWe analyzed Spf.com page load time and found that the first response time was 264 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
spf.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value9.9 s
0/100
25%
Value10.1 s
9/100
10%
Value650 ms
45/100
30%
Value0.345
32/100
15%
Value13.9 s
10/100
10%
264 ms
514 ms
301 ms
212 ms
183 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Spf.com, 32% (35 requests) were made to Demandware.edgesuite.net and 9% (10 requests) were made to Myspringfield.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Demandware.edgesuite.net.
Page size can be reduced by 1.4 MB (22%)
6.6 MB
5.2 MB
In fact, the total size of Spf.com main page is 6.6 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 4.7 MB which makes up the majority of the site volume.
Potential reduce by 169.2 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 169.2 kB or 86% of the original size.
Potential reduce by 15.5 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. Spf images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 73% of the original size.
Potential reduce by 199.4 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. Spf.com needs all CSS files to be minified and compressed as it can save up to 199.4 kB or 81% of the original size.
Number of requests can be reduced by 30 (32%)
95
65
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
spf.com
264 ms
es
514 ms
jquery-ui.min.css
301 ms
modernizr-custom.js
212 ms
fonts.css
183 ms
style.css
516 ms
dwac-14.8.js
205 ms
build.min.js
59 ms
jquery-2.1.4.min.js
550 ms
jquery-ui.min.js
571 ms
jquery.validate.min.js
238 ms
jquery.cookie.js
144 ms
jquery.zoom.min.js
241 ms
app.js
656 ms
dwanalytics.js
383 ms
gretel.min.js
6 ms
fly_es_es_man.jpg
269 ms
logo-spf.png
187 ms
home-banner1-20160314-mb.jpg
469 ms
home-banner2-20160314-A.jpg
609 ms
home-banner2-20160314-B.jpg
467 ms
home-banner4-20160314-mb.jpg
536 ms
tile-placeholder.gif
427 ms
fly_es_es_woman.jpg
236 ms
fly_es_man_sale.jpg
255 ms
fly_es_woman_sale.jpg
279 ms
20160203_fly_myspf.jpg
281 ms
gtm.js
196 ms
ajax-loader.gif
514 ms
ajax-loader2.gif
515 ms
P_099750110C.jpg
530 ms
P_099750199C.jpg
634 ms
P_099750118C.jpg
583 ms
P_299705312C.jpg
584 ms
P_299705345C.jpg
644 ms
proximanova-bold-webfont.woff
371 ms
proximanova-regular-webfont.woff
371 ms
icomoon.ttf
427 ms
bebasneue_bold_0-webfont.woff
454 ms
protimient_-_eksja-webfont.woff
436 ms
proximanova-light-webfont.woff
358 ms
ea53fd96053dd6b8dd3e0ec30a3caa55
250 ms
404
427 ms
8162.js
9 ms
analytics.js
24 ms
tag.js
219 ms
ec.js
11 ms
collect
12 ms
collect
191 ms
s
113 ms
home-banner1-20160314.jpg
916 ms
home-banner3-20160314.jpg
2321 ms
home-banner4-20160314.jpg
1087 ms
P_841734209FL.jpg
916 ms
P_007712710FL.jpg
738 ms
P_795734316FL.jpg
1010 ms
P_005718555FL.jpg
979 ms
P_099750110FL.jpg
1146 ms
P_175709112FL.jpg
1161 ms
P_009793411FL.jpg
1232 ms
P_299705312FL.jpg
1262 ms
u
178 ms
ea53fd96053dd6b8dd3e0ec30a3caa55
167 ms
capture-apps-4.12.11.js
42 ms
iframeStorage.html
141 ms
375F1B13-4594-45D7-9914-2F926EC42D23
386 ms
build.min.css
30 ms
recent
60 ms
iframeStorage.js
8 ms
render.gif
79 ms
mobile.jpg
338 ms
mobile.jpg
162 ms
mobile.jpg
245 ms
mobile.jpg
159 ms
video-controls.png
69 ms
favicon.ico
68 ms
mobile.jpg
303 ms
mobile.jpg
333 ms
mobile.jpg
313 ms
mobile.jpg
312 ms
mobile.jpg
351 ms
mobile.jpg
714 ms
mobile.jpg
233 ms
mobile.jpg
233 ms
mobile.jpg
263 ms
mobile.jpg
262 ms
mobile.jpg
266 ms
mobile.jpg
269 ms
mobile.jpg
375 ms
mobile.jpg
448 ms
mobile.jpg
270 ms
mobile.jpg
271 ms
mobile.jpg
270 ms
mobile.jpg
377 ms
mobile.jpg
295 ms
mobile.jpg
293 ms
mobile.jpg
293 ms
viewer2v2.html
229 ms
BebasNeue.woff
26 ms
olapic-icons.woff
93 ms
Roboto.woff
152 ms
appsmanagerinit
258 ms
__Analytics-Tracking
117 ms
collect
24 ms
collect
24 ms
ld.js
30 ms
ga-audiences
33 ms
event
21 ms
event
176 ms
spf.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA IDs 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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
spf.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
spf.com 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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spf.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Spf.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.
spf.com
Open Graph data is detected on the main page of Spf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: