3.9 sec in total
714 ms
2.4 sec
831 ms
Welcome to surface.com homepage info - get ready to check Surface best content for United States right away, or after learning these important things about surface.com
Discover Microsoft Surface Copilot+ PCs, laptops, 2-in-1s, and computers built for all the ways you work, play, create, and connect.
Visit surface.comWe analyzed Surface.com page load time and found that the first response time was 714 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
surface.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value14.3 s
0/100
25%
Value13.6 s
2/100
10%
Value15,560 ms
0/100
30%
Value0.004
100/100
15%
Value33.2 s
0/100
10%
714 ms
84 ms
71 ms
61 ms
60 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Surface.com, 22% (29 requests) were made to Assets.adobedtm.com and 22% (29 requests) were made to Cdn-dynmedia-1.microsoft.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn-dynmedia-1.microsoft.com.
Page size can be reduced by 740.2 kB (17%)
4.3 MB
3.6 MB
In fact, the total size of Surface.com main page is 4.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. Only a small number of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 422.4 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 79.0 kB, which is 16% 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 422.4 kB or 87% of the original size.
Potential reduce by 12.7 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. Surface images are well optimized though.
Potential reduce by 305.1 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 305.1 kB or 22% of the original size.
Number of requests can be reduced by 85 (72%)
118
33
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Surface. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
surface
714 ms
main-light.min.ACSHASHfd071803266ba1f4336b43868366299a.css
84 ms
clientlib-base.min.ACSHASHe96ed1b9d8202d1637334f39946f7f10.css
71 ms
clientlib-site.min.ACSHASH93513bf809e3fbdc2661b36786949a5f.css
61 ms
clientlib-surface.min.ACSHASHf04c9524598b58460481a041302f72fb.css
60 ms
clientlib-uhf.min.ACSHASHf9f2395c582fa601707b7a5dfae9f05f.css
60 ms
clientlib-experimentations.min.ACSHASHdf20eb81fa2af3a1c0b0246a9a6a9485.css
59 ms
clientlib-jquery.min.ACSHASH35986a813756f39ab6b922979ffedb03.js
130 ms
clientlib-jquery-cookie.min.ACSHASH20aafdf6904d3dc5db0e0e33abbfc1a4.js
115 ms
launch-EN7506e353034849faa4a18bc4c20e727c.min.js
37 ms
v1.min.ACSHASH4cffc2c9b55f8bde649e0d2535a1eebd.js
117 ms
v1.min.ACSHASHc343dfb005ac8c14ae0dd22dd17fb2fc.js
115 ms
7a-c9e644
122 ms
site.min.ACSHASH1dabd5cc3f7b68c178b59ea74dc62947.js
119 ms
site.min.ACSHASH969435394b30c580ff6a3f01db878521.css
118 ms
site.min.ACSHASH8fe9b76c8f32adfb2e047324ab58bc79.js
119 ms
site.min.ACSHASH670327b1289477b531f58308679ce696.css
120 ms
site.min.ACSHASHb3791966d88d89cca3b3215635892e62.js
217 ms
site.min.ACSHASH0e0171efe5e80d068bc4ca312df31333.css
214 ms
webchat.js
74 ms
site.min.ACSHASH2ef2f8dd5326d8e57ddc7e8e50f9b76c.js
214 ms
site.min.ACSHASH948479e060a1dbc480dfe75ac1d8c90b.css
213 ms
site.min.ACSHASH3998f3124dafc8ff9ea50108406f576e.css
296 ms
site.min.ACSHASHd1c00582e60ff4999552981d6fca8131.css
360 ms
site.min.ACSHASH85163f649c93355720a2337ccddda59f.js
298 ms
site.min.ACSHASH4c1157fc4d014852194996b7ab7d2c75.js
297 ms
sites.min.ACSHASHf16c097bfb9c7021f04489c3db8fa08e.css
295 ms
sites.min.ACSHASH8e742d11d6b24c401e35f3b516726584.js
296 ms
site.min.ACSHASHfcd864419c73e762b5aee2e50a732254.css
296 ms
site.min.ACSHASH8ee0e1947ab2522746cba2c424609566.js
296 ms
site.min.ACSHASH5b877f84fd27d2e8c2af7b1c31a817a0.css
298 ms
site.min.ACSHASH791590c1a45563ecff51918c2fde2262.js
297 ms
site.min.ACSHASH348b07e6e2c5729e9e932ba2765bdf43.js
355 ms
site.min.ACSHASHf834ecc43df9754fbcd8a6bb1078e89e.js
354 ms
site.min.ACSHASH189a5869dc44161e38ed1312909e1b40.css
354 ms
site.min.ACSHASH49ac89db81d6473db4bbc6036520e018.js
433 ms
site.min.ACSHASHebc5e4020229b2f0acef286deb9fe719.css
432 ms
clientlib-store.min.ACSHASH0b901a261cbeb1d3be6852ed908f640f.css
432 ms
wcp-consent.js
98 ms
meversion
287 ms
site.min.ACSHASH40203e0bb3e24fd4626d84825f55e9c5.css
428 ms
sites.min.ACSHASHa722775809d2312f435036def15bcd62.css
388 ms
site.min.ACSHASHe792f21105d152bbb1e64c0cd25549ac.js
387 ms
clientlib-store.min.ACSHASH93e1b4ab986106dc57b0570136b64c7e.js
774 ms
site.min.ACSHASHca0820e0b24021397ac8910bbd5a1f49.js
774 ms
site.min.ACSHASHec8aed9df755a7b27e52317dcf532df8.js
369 ms
sites.min.ACSHASH48d949b834ed32dfd8266989e9dab912.js
334 ms
6c-7627b9
794 ms
main-light.min.ACSHASHe3fd481804126aad70e99fe060fe8dca.js
824 ms
clientlib-base.min.ACSHASHbefe94bb74f320523b985d2f5ec1db26.js
717 ms
clientlib-site.min.ACSHASHff9cacb22668c4f6174e0af4a2be89f9.js
712 ms
clientlib-surface.min.ACSHASH1528cf251d2f5f70e2d302c321a1313a.js
788 ms
clientlib-experimentations.min.ACSHASH42a66d9f9ada368ff1f223c79bed95cf.js
787 ms
clientlib-httpclient.min.ACSHASHa5733ba5736ab47d9c9ec8fd1bf8719c.js
786 ms
clientlib-cookieconsent.min.ACSHASH96f0c5b1219e39b8788028f5c17a5ad9.js
785 ms
RE1Mu3b
229 ms
surfcon-home-hero-FY24-may-mobile-1
624 ms
ADO220440334_Tentpole_Title_Retargeting_MLB_The_Show_MSLogo
698 ms
pro-9-platinum-hero-mobile-FY24
838 ms
laptop-go-3-platinum-hero-mobile-FY24
1215 ms
laptop-5-15-platinum-hero-mobile-FY24
836 ms
laptop-studio-2-hero-mobile-FY24
836 ms
studio-2-plus-hero-mobile-FY24
931 ms
MSFT-home-ql-compare-svgicon
697 ms
MSFT-home-ql-hmc-svgicon
728 ms
MSFT-home-ql-deals-svgicon
830 ms
MSFT-home-ql-why-surface-svgicon
935 ms
MSFT-home-ql-business-svgicon
931 ms
MSFT-home-ql-accessibility-svgicon
1108 ms
Surface-Pro-9-AI-copilot-new:VP1-1078x606
956 ms
MSFT-Surface-Adaptive-Accessories-Home-Accessibilty-Poster
940 ms
MSFT-Surface-Adaptive-Accessories-Home-Accessibilty-Poster-2
954 ms
MSFT-Surface-prefooter-protect-svgicon
945 ms
MSFT-Surface-prefooter-business-svgicon
940 ms
MSFT-Surface-prefooter-accessories-svgicon
943 ms
MSFT-surface-prefooter-support-svgicon
947 ms
MSFT-Surface-prefooter-register-svgicon
949 ms
MSFT-Surface-prefooter-newsletter-svgicon
952 ms
MSFT-Power-cord-recall-icon-1
950 ms
953 ms
Icon_NewsSocial_68x68
956 ms
955 ms
956 ms
featurecontrol.min.ACSHASHc22ea5b46f3fcad90da0abcc0a3f73d4.js
830 ms
custom-oneds.min.ACSHASHb4f0b5100b03a879dd5d2e97636efc37.js
828 ms
clientlib-greenid.min.ACSHASH383b23d12df0d9265d7569a7102c2f96.js
822 ms
ie11-polyfills.js
745 ms
744 ms
latest.woff
501 ms
latest.woff
632 ms
latest.woff
636 ms
latest.woff
743 ms
latest.woff
742 ms
latest.woff
740 ms
latest.woff
741 ms
latest.woff
737 ms
latest.woff
736 ms
mwfmdl2-v3.54.woff
634 ms
MWFFluentIcons.woff
745 ms
Surface_Pro-9_tablet_platinum_angled-render_with-Surface-Pen_mobile
489 ms
Surface_Laptop-5-13.5_platinum_angled-render_mobile
382 ms
ms.shared.analytics.mectrl-3.gbl.min.js
129 ms
RCf9d4fd36645544efa0585a0aa8420705-source.min.js
53 ms
RCa3837734c6744578a4cd813563579094-source.min.js
92 ms
RCaea9defea3ec4379976c7cfe2b2eaa7a-source.min.js
100 ms
RC4eca6d570e2d4f919d49e225bf4ba061-source.min.js
100 ms
RCbb43ab0df0dc49d88347b60b3b8cda8a-source.min.js
100 ms
RC502239fc70c04e1281d103f80e0e7386-source.min.js
102 ms
RC0b7731cdab3f4adfbeaf0b120ee35714-source.min.js
103 ms
RC1eb56fbe10104e50b3bfd9e098e96a53-source.min.js
101 ms
RC508ef9af51f14d99a50e4f8c13ea404d-source.min.js
104 ms
RCdc5dfc7e9fe0429fb792428307bc5385-source.min.js
104 ms
RCf4e8ddb48e17419cb41d2d069084e732-source.min.js
99 ms
RCf07f548ff3904e6aae2cc165a2846cfc-source.min.js
101 ms
RC896555a3a6fd4270bd6d5e1793496d98-source.min.js
100 ms
RC736097a8d04f4160917c7a6abefa3186-source.min.js
101 ms
RC4d692ba452954573954b9298b31cdb9c-source.min.js
100 ms
RC03cb138b5d0c439f85682029c8e592fc-source.min.js
106 ms
RCfc4f5efe27954b64a7a11d87e06cdd14-source.min.js
106 ms
RC0b89b86225eb4122812bba8e94f80a32-source.min.js
105 ms
RC76581c113f0946488673bcaeca24b725-source.min.js
109 ms
RCe7ed6de90a0d42abbfd7742b6280ce25-source.min.js
104 ms
RC73e8eba2c60442d5ac8f76988debb91c-source.min.js
105 ms
RCa26d541cf4ca4821943cfedadab3fb0a-source.min.js
106 ms
RCe6ead21b5c864be99dbf9cf91e7514a1-source.min.js
103 ms
RC91b56739d1084ddf9e7f940073391f23-source.min.js
103 ms
RCce780b2ea8aa4d55a7c135c9b8dc4333-source.min.js
102 ms
RCf45be8e1e9f44c998e8838d62a6d8472-source.min.js
101 ms
RC7550d325dffa49d4939977ff4cb148b4-source.min.js
103 ms
RCf0b30611a7f849febaa248427b2002ee-source.min.js
103 ms
surface.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
surface.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
Missing source maps for large first-party JavaScript
surface.com SEO score
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 Surface.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 Surface.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.
surface.com
Open Graph data is detected on the main page of Surface. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: