2.1 sec in total
68 ms
1 sec
982 ms
Welcome to 1220.com homepage info - get ready to check 1220 best content right away, or after learning these important things about 1220.com
Because your exhibits deserve expert fabricators. Learn More The 1220 team Expertise and Premium Quality With 50 years of experience, the 1220 team is held to higher standards when it comes to project...
Visit 1220.comWe analyzed 1220.com page load time and found that the first response time was 68 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
1220.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value6.1 s
12/100
25%
Value4.8 s
67/100
10%
Value970 ms
28/100
30%
Value0.011
100/100
15%
Value12.3 s
15/100
10%
68 ms
147 ms
35 ms
53 ms
51 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 72% of them (75 requests) were addressed to the original 1220.com, 20% (21 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (364 ms) belongs to the original domain 1220.com.
Page size can be reduced by 146.5 kB (15%)
970.8 kB
824.2 kB
In fact, the total size of 1220.com main page is 970.8 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. 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 634.4 kB which makes up the majority of the site volume.
Potential reduce by 101.7 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 101.7 kB or 84% of the original size.
Potential reduce by 3.6 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. 1220 images are well optimized though.
Potential reduce by 19.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 19.2 kB or 24% of the original size.
Potential reduce by 22.2 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. 1220.com needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 16% of the original size.
Number of requests can be reduced by 52 (66%)
79
27
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1220. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
1220.com
68 ms
1220.com
147 ms
wp-emoji-release.min.js
35 ms
style.min.css
53 ms
style.min.css
51 ms
theme.min.css
57 ms
frontend-lite.min.css
184 ms
post-6.css
61 ms
elementor-icons.min.css
73 ms
frontend-lite.min.css
44 ms
global.css
45 ms
post-83.css
50 ms
post-42.css
59 ms
post-71.css
57 ms
style.css
55 ms
ecs-style.css
54 ms
post-1426.css
69 ms
css
79 ms
fontawesome.min.css
58 ms
solid.min.css
64 ms
brands.min.css
64 ms
jquery.min.js
63 ms
jquery-migrate.min.js
69 ms
ecs_ajax_pagination.js
66 ms
ecs.js
64 ms
widget-nav-menu.min.css
94 ms
widget-carousel.min.css
63 ms
widget-icon-list.min.css
66 ms
e-gallery.min.css
68 ms
master-addons-styles.css
67 ms
hello-frontend.min.js
69 ms
jquery.smartmenus.min.js
71 ms
e-gallery.min.js
70 ms
imagesloaded.min.js
73 ms
webpack-pro.runtime.min.js
88 ms
webpack.runtime.min.js
83 ms
frontend-modules.min.js
83 ms
regenerator-runtime.min.js
85 ms
wp-polyfill.min.js
82 ms
hooks.min.js
84 ms
i18n.min.js
68 ms
frontend.min.js
67 ms
waypoints.min.js
66 ms
core.min.js
62 ms
frontend.min.js
56 ms
elements-handlers.min.js
56 ms
jquery.sticky.min.js
316 ms
plugins.js
72 ms
master-addons-scripts.js
51 ms
gtm.js
212 ms
logo-white.png
114 ms
1220-logo-default1.png
115 ms
banner-background-image.jpg
117 ms
home-2-683x1024.jpg
156 ms
home-1-683x1024.jpg
118 ms
what-we-do-image.jpg
157 ms
project-management-icon.png
114 ms
Technical-150x150.png
120 ms
Audio-Visual-300x300.png
119 ms
Account-Management-40x40-1.png
148 ms
icon9.png
148 ms
Graphic-Design.png
148 ms
interactives-icon.png
147 ms
Metal-40x40-1.png
155 ms
CNC-40x40-1.png
154 ms
installation-icon.png
154 ms
icon3.png
154 ms
Graphics-Production-40x40-1.png
165 ms
Shipping-40x40-1.png
203 ms
Finishing-40x40-1.png
364 ms
Scenic-Production-40x40-1.png
164 ms
quote-left.png
165 ms
placeholder.png
164 ms
quote-right.png
167 ms
logo.png
168 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
65 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
100 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
126 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
148 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
249 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
250 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
249 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
249 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
248 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
249 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
253 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
249 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
253 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
252 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
251 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
250 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
253 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
255 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
256 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
254 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
253 ms
fa-brands-400.woff
61 ms
fa-solid-900.woff
61 ms
20125109.js
224 ms
js
110 ms
20125109.js
119 ms
conversations-embed.js
76 ms
collectedforms.js
76 ms
20125109.js
127 ms
1220.com 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
Links do not have a discernible name
1220.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
1220.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1220.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 1220.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.
1220.com
Open Graph data is detected on the main page of 1220. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: