885 ms in total
17 ms
715 ms
153 ms
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 17 ms and then it took 868 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
212areacode.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.7 s
33/100
25%
Value5.6 s
53/100
10%
Value350 ms
73/100
30%
Value0.099
90/100
15%
Value8.1 s
41/100
10%
17 ms
89 ms
67 ms
65 ms
52 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 79% of them (58 requests) were addressed to the original 212areacode.com, 16% (12 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 (320 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 260.9 kB (40%)
649.1 kB
388.2 kB
In fact, the total size of 212areacode.com main page is 649.1 kB. 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. HTML takes 314.2 kB which makes up the majority of the site volume.
Potential reduce by 260.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 260.2 kB or 83% of the original size.
Potential reduce by 8 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. 212 Area Code images are well optimized though.
Potential reduce by 674 B
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 has all CSS files already compressed.
Number of requests can be reduced by 28 (58%)
48
20
The browser has sent 48 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 6 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
212areacode.com
17 ms
212areacode.com
89 ms
style.min.css
67 ms
wc-blocks-vendors-style.css
65 ms
wc-blocks-style.css
52 ms
css
50 ms
followups.css
62 ms
public-main.css
71 ms
yith_wcas_ajax_search.css
73 ms
bootstrap.min.css
65 ms
style.css
94 ms
style.css
73 ms
dynamic.css
71 ms
vtmin-error-style.css
75 ms
sv-wc-payment-gateway-payment-form.min.css
88 ms
js_composer.min.css
129 ms
sccss.css
89 ms
Defaults.css
87 ms
ultimate.min.css
110 ms
icons.css
110 ms
font-awesome.min.css
155 ms
plugins.css
144 ms
responsive.css
149 ms
jquery.min.js
168 ms
jquery-migrate.min.js
166 ms
wassup-widget.css
166 ms
font-awesome.css
162 ms
rs6.css
241 ms
jquery.blockUI.min.js
242 ms
jquery.payment.min.js
241 ms
wp-embed.min.js
242 ms
lazyload.min.js
242 ms
dummy.png
119 ms
Raleway-Regular.ttf
117 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
156 ms
Raleway-Medium.ttf
117 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
237 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
320 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
319 ms
RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff
320 ms
Raleway-SemiBold.ttf
153 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
262 ms
Raleway-Bold.ttf
154 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
261 ms
Raleway-ExtraBold.ttf
153 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
261 ms
PKCRbVvRfd5n7BTjtGiFZBsxEYwM7FgeyaSgU71cLG0.woff
265 ms
Raleway-RegularItalic.ttf
143 ms
Raleway-MediumItalic.ttf
142 ms
Raleway-LightItalic.ttf
141 ms
fontawesome-webfont.woff
141 ms
fontawesome-webfont.woff
141 ms
H4ckBXKAlMnTn0CskxY9yLs.ttf
147 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf
147 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
199 ms
123 ms
iheart121212.png
39 ms
iheart212header.png
94 ms
wallsj-logo.jpg
39 ms
tnyt-logo.jpg
39 ms
daily-news.jpg
94 ms
cbs-new-york.jpg
41 ms
ico1-1.png
89 ms
ico2-1.png
94 ms
ico3-1.png
93 ms
ico4-1.png
96 ms
voip1.png
95 ms
voip1.jpg
95 ms
virtualnew.jpg
96 ms
landlines3.jpg
98 ms
footerlogoiheart212.png
98 ms
badge.png
96 ms
42 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
212areacode.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
212areacode.com SEO score
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: