15.2 sec in total
1.4 sec
11.7 sec
2 sec
Visit 212areacode.com now to see the best up-to-date 212 Area Code content for United States and also check out these interesting facts you probably never knew about 212areacode.com
Featured in The NYT, WSJ & CNN | Buy and get a New York City, Manhattan 212 area code phone number for your business, cell phone, VoIP & Google Voice.
Visit 212areacode.comWe analyzed 212areacode.com page load time and found that the first response time was 1.4 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
212areacode.com performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value37.1 s
0/100
25%
Value71.2 s
0/100
10%
Value97,560 ms
0/100
30%
Value0.074
95/100
15%
Value118.0 s
0/100
10%
1427 ms
235 ms
421 ms
310 ms
414 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 81% of them (87 requests) were addressed to the original 212areacode.com, 11% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 607.6 kB (55%)
1.1 MB
498.2 kB
In fact, the total size of 212areacode.com main page is 1.1 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. 85% 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. CSS take 707.8 kB which makes up the majority of the site volume.
Potential reduce by 162.8 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 162.8 kB or 84% of the original size.
Potential reduce by 3.0 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. 212 Area Code images are well optimized though.
Potential reduce by 11.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. This website has mostly compressed JavaScripts.
Potential reduce by 430.7 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. 212areacode.com needs all CSS files to be minified and compressed as it can save up to 430.7 kB or 61% of the original size.
Number of requests can be reduced by 57 (70%)
81
24
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 212 Area Code. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
212areacode.com
1427 ms
style.min.css
235 ms
wc-blocks-vendors-style.css
421 ms
wc-blocks-style.css
310 ms
followups.css
414 ms
public-main.css
414 ms
yith_wcas_ajax_search.css
809 ms
bootstrap.min.css
739 ms
style.css
506 ms
style.css
499 ms
dynamic.css
738 ms
vtmin-error-style.css
835 ms
sv-wc-payment-gateway-payment-form.min.css
843 ms
js_composer.min.css
1133 ms
Defaults.css
1360 ms
ultimate.min.css
885 ms
icons.css
1064 ms
font-awesome.min.css
1365 ms
plugins.css
1431 ms
responsive.css
1478 ms
jquery.min.js
1478 ms
jquery-migrate.min.js
1411 ms
fue-account-subscriptions.js
1473 ms
public-main.js
1408 ms
wpm-public.p1.min.js
1912 ms
vtmin-clear-cart-msgs.js
1912 ms
core.min.js
1914 ms
ultimate.min.js
1956 ms
ultimate_bg.min.js
1999 ms
modernizr.js
1892 ms
head.min.js
1938 ms
wassup-widget.css
1890 ms
snippet.js
1260 ms
css
1809 ms
font-awesome.css
2375 ms
rs6.css
2348 ms
comment-reply.min.js
2341 ms
jquery.selectBox.min.js
2342 ms
jquery.prettyPhoto.min.js
2362 ms
jquery.yith-wcwl.min.js
2270 ms
rbtools.min.js
2150 ms
rs6.min.js
2154 ms
fue-front.js
2094 ms
jquery.blockUI.min.js
2098 ms
js.cookie.min.js
1826 ms
woocommerce.min.js
1824 ms
cart-fragments.min.js
1820 ms
yith-autocomplete.min.js
1810 ms
underscore.min.js
1811 ms
wp-util.min.js
1776 ms
add-to-cart-variation.min.js
1754 ms
etheme-new.min.js
1514 ms
jquery.payment.min.js
1281 ms
sv-wc-payment-gateway-payment-form.js
1259 ms
wc-gateway-ppec-order-review.js
1252 ms
plugins.min.js
1861 ms
hoverIntent.min.js
1844 ms
wp-embed.min.js
1797 ms
js_composer_front.min.js
1783 ms
1022 ms
small-close.png
830 ms
iheart121212.png
830 ms
hot-menu.png
832 ms
iheart212header.png
831 ms
dummy.png
914 ms
wallsj-logo.jpg
965 ms
tnyt-logo.jpg
883 ms
daily-news.jpg
882 ms
cbs-new-york.jpg
953 ms
ico1-1.png
879 ms
ico2-1.png
962 ms
ico3-1.png
989 ms
ico4-1.png
988 ms
voip1.png
960 ms
voip1.jpg
987 ms
virtualnew.jpg
956 ms
landlines3.jpg
955 ms
footerlogoiheart212.png
953 ms
badge.png
951 ms
Raleway-Regular.ttf
650 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
1709 ms
Raleway-Medium.ttf
648 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
2342 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
2342 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
2376 ms
RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff
2340 ms
Raleway-SemiBold.ttf
1686 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
2318 ms
Raleway-Bold.ttf
1707 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
2319 ms
Raleway-ExtraBold.ttf
1683 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
2353 ms
PKCRbVvRfd5n7BTjtGiFZBsxEYwM7FgeyaSgU71cLG0.woff
2352 ms
fontawesome-webfont.woff
1680 ms
Raleway-RegularItalic.ttf
1683 ms
Raleway-MediumItalic.ttf
1681 ms
Raleway-LightItalic.ttf
2316 ms
2260 ms
h-line.jpg
791 ms
ga.js
461 ms
__utm.gif
99 ms
952d755a-5f02-4a41-9eeb-8d609a8df9af
736 ms
collect
283 ms
H4ckBXKAlMnTn0CskxY9yLs.ttf
465 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf
71 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
72 ms
ga-audiences
388 ms
fontawesome-webfont.woff
57 ms
212areacode.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
212areacode.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
212areacode.com 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 212areacode.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 212areacode.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.
212areacode.com
Open Graph description is not detected on the main page of 212 Area Code. 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: