3.1 sec in total
478 ms
2.2 sec
450 ms
Welcome to portillos.com homepage info - get ready to check Portillo S best content for United States right away, or after learning these important things about portillos.com
Portillo's is home to America's favorite Italian beef, burgers, salads, Chicago-style hot dogs, and chocolate cake.
Visit portillos.comWe analyzed Portillos.com page load time and found that the first response time was 478 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
portillos.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value45.5 s
0/100
25%
Value15.7 s
0/100
10%
Value2,330 ms
5/100
30%
Value0.27
45/100
15%
Value60.8 s
0/100
10%
478 ms
24 ms
43 ms
58 ms
247 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 34% of them (30 requests) were addressed to the original Portillos.com, 22% (20 requests) were made to Scontent.cdninstagram.com and 15% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (652 ms) relates to the external source Api.instagram.com.
Page size can be reduced by 1.3 MB (26%)
5.0 MB
3.7 MB
In fact, the total size of Portillos.com main page is 5.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. 80% 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 3.3 MB which makes up the majority of the site volume.
Potential reduce by 122.1 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 19.3 kB, which is 12% 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 122.1 kB or 75% of the original size.
Potential reduce by 49.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. Portillo S images are well optimized though.
Potential reduce by 676.4 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 676.4 kB or 64% of the original size.
Potential reduce by 425.8 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. Portillos.com needs all CSS files to be minified and compressed as it can save up to 425.8 kB or 85% of the original size.
Number of requests can be reduced by 24 (34%)
70
46
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portillo S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.portillos.com
478 ms
css
24 ms
css
43 ms
css
58 ms
FileMerge.axd
247 ms
FileMerge.axd
374 ms
WebResource.axd
4 ms
swfobject.js
5 ms
ScriptResource.axd
5 ms
ScriptResource.axd
6 ms
js
80 ms
addthis_widget.js
9 ms
153 ms
652 ms
close.png
4 ms
loading.gif
5 ms
prev.png
6 ms
next.png
5 ms
logo-top-2.png
50 ms
logo-top-3.png
49 ms
Catering_banner_v1.2-2.png
5 ms
history-bn1.gif
21 ms
shipping_banner.png
24 ms
join-us-bn1.gif
21 ms
db64a728e1e542c7bfa1a01eff0b27e11.png
24 ms
Cubs_21.jpg
22 ms
gift-card.gif
23 ms
gtm.js
33 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
36 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
64 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
90 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
87 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
90 ms
hawksearch.min.js
162 ms
analytics.js
23 ms
conversion_async.js
17 ms
fbds.js
4 ms
112 ms
48 ms
collect
16 ms
collect
68 ms
41 ms
ga-audiences
16 ms
jquery-1.11.0_jquery-ui-slider-1.10.4.min.js
105 ms
ajax.aspx
30 ms
icomoon.ttf
25 ms
icomoon.woff
27 ms
icomoon.woff
93 ms
BHG8ZtTfO0yYnp02--QxqqCWcynf_cDxXwCLxiixG1c.ttf
26 ms
sprite-1.png
66 ms
PepperEggHomepage.png
70 ms
cake-sign-up.png
67 ms
575396004649955328
186 ms
7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf
107 ms
12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf
108 ms
W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf
109 ms
OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf
108 ms
t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf
108 ms
bmC0pGMXrhphrZJmniIZpZ0EAVxt0G0biEntp43Qt6E.ttf
108 ms
ftr_logo.png
68 ms
_Incapsula_Resource
166 ms
addthis_widget.js
135 ms
300lo.json
132 ms
sh.7c7179124ea24ac6ba46caac.html
127 ms
1f35f.png
149 ms
_Incapsula_Resource
103 ms
12747643_832626563526888_1544521964_n.jpg
165 ms
1f354.png
95 ms
12749930_198789623813605_1801672751_n.jpg
107 ms
12783349_1522312134730647_1337469860_n.jpg
160 ms
12783958_1590653507877530_1424283921_n.jpg
142 ms
1516619_1682846478620101_874339611_n.jpg
142 ms
12749886_1700538676899921_2118618132_n.jpg
146 ms
12724999_1666102203663681_1669827140_n.jpg
160 ms
12716589_174148272961954_1756869785_n.jpg
346 ms
12716608_587943348031260_1974475604_n.jpg
175 ms
12716661_168138196898697_1602483882_n.jpg
178 ms
12677609_1046204962112161_1684863963_n.jpg
162 ms
12717101_1557349731245144_776011618_n.jpg
176 ms
12717041_224518784561835_884087410_n.jpg
194 ms
12628119_1163708013641811_625837805_n.jpg
210 ms
12725137_1678841492398229_1682759332_n.jpg
210 ms
12677661_1690349291242534_281675449_n.jpg
229 ms
12599224_1071660646228246_2072163325_n.jpg
210 ms
12628080_209974236022212_4021332_n.jpg
245 ms
12534444_916948328420077_1900419302_n.jpg
255 ms
12677141_1691459147794143_1137155038_n.jpg
244 ms
24 ms
portillos.com 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
Image elements do not have [alt] attributes
portillos.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
Page has valid source maps
portillos.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
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portillos.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 Portillos.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.
portillos.com
Open Graph description is not detected on the main page of Portillo S. 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: