8.7 sec in total
734 ms
7.7 sec
295 ms
Click here to check amazing Homeslice content. Otherwise, check out these important facts you probably never knew about homeslice.pizza
Homeslice Pizza
Visit homeslice.pizzaWe analyzed Homeslice.pizza page load time and found that the first response time was 734 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
homeslice.pizza performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value20.3 s
0/100
25%
Value17.6 s
0/100
10%
Value420 ms
66/100
30%
Value0.069
96/100
15%
Value18.6 s
3/100
10%
734 ms
2464 ms
485 ms
688 ms
688 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 89% of them (62 requests) were addressed to the original Homeslice.pizza, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Api.instagram.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Homeslice.pizza.
Page size can be reduced by 1.0 MB (46%)
2.3 MB
1.2 MB
In fact, the total size of Homeslice.pizza main page is 2.3 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. 55% of websites need less resources to load. Images take 865.5 kB which makes up the majority of the site volume.
Potential reduce by 35.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. 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 35.1 kB or 76% of the original size.
Potential reduce by 811 B
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. Homeslice images are well optimized though.
Potential reduce by 560.2 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 560.2 kB or 65% of the original size.
Potential reduce by 446.6 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. Homeslice.pizza needs all CSS files to be minified and compressed as it can save up to 446.6 kB or 86% of the original size.
Number of requests can be reduced by 49 (78%)
63
14
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homeslice. 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 26 to 1 for CSS and as a result speed up the page load time.
homeslice.pizza
734 ms
homeslice.pizza
2464 ms
wp-emoji-release.min.js
485 ms
styles.css
688 ms
sb-instagram.css
688 ms
font-awesome.min.css
46 ms
settings.css
1174 ms
style.css
706 ms
base.css
708 ms
buttons.css
719 ms
mfn-icons.css
1147 ms
grid.css
919 ms
layout.css
1414 ms
shortcodes.css
1418 ms
variables.css
958 ms
style-simple.css
1153 ms
animations.min.css
1430 ms
colorpicker.css
1378 ms
jquery.ui.all.css
1383 ms
jplayer.blue.monday.css
1410 ms
prettyPhoto.css
1610 ms
responsive.css
1617 ms
style-colors.php
1725 ms
style.php
1717 ms
css
45 ms
css
63 ms
custom.css
1656 ms
style.css
1672 ms
responsive-1240.css
1846 ms
jquery.js
2077 ms
jquery-migrate.min.js
1897 ms
jquery.themepunch.tools.min.js
2143 ms
jquery.themepunch.revolution.min.js
1984 ms
jquery.form.min.js
1726 ms
scripts.js
1858 ms
sb-instagram.js
1907 ms
core.min.js
1982 ms
widget.min.js
2078 ms
mouse.min.js
2079 ms
sortable.min.js
2148 ms
js
89 ms
tabs.min.js
2151 ms
accordion.min.js
1955 ms
jquery.plugins.js
2467 ms
animations.min.js
1866 ms
jquery.jplayer.min.js
2074 ms
colorpicker.js
1922 ms
mfn.menu.js
1910 ms
scripts.js
1761 ms
comment-reply.min.js
1823 ms
mobi2go.js
1720 ms
fbevents.js
36 ms
homeslice-instagram.png
668 ms
homeslice-twitter.png
720 ms
homeslice-facebook.png
807 ms
homeslice-logo.png
813 ms
homeslice-banner.jpg
1373 ms
wannagetfresh.png
907 ms
line-break.png
1020 ms
orderatastysalad.png
1039 ms
Homeslice-logo-foot.png
1045 ms
loader.png
1130 ms
kapra-regular-webfont.woff
1162 ms
relative-medium-webfont.woff
1170 ms
1604871454
119 ms
recent
168 ms
mfn-icons.woff
1412 ms
homeslicepizza.js
1539 ms
tp-leftarrow.png
263 ms
tp-rightarrow.png
371 ms
homeslice.pizza 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
homeslice.pizza 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
homeslice.pizza SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Homeslice.pizza 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 Homeslice.pizza 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.
homeslice.pizza
Open Graph description is not detected on the main page of Homeslice. 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: