2.7 sec in total
32 ms
1.4 sec
1.2 sec
Visit epam.am now to see the best up-to-date EPAM content for Armenia and also check out these interesting facts you probably never knew about epam.am
Since 1993, we've helped customers digitally transform their businesses through our unique blend of world-class software engineering, design and consulting services.
Visit epam.amWe analyzed Epam.am page load time and found that the first response time was 32 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
epam.am performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value23.1 s
0/100
25%
Value11.2 s
5/100
10%
Value2,740 ms
3/100
30%
Value0.023
100/100
15%
Value17.5 s
4/100
10%
32 ms
69 ms
33 ms
34 ms
43 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Epam.am, 86% (90 requests) were made to Epam.com and 10% (10 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (847 ms) relates to the external source Googletagmanager.com.
Page size can be reduced by 415.2 kB (64%)
649.9 kB
234.7 kB
In fact, the total size of Epam.am main page is 649.9 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. 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. HTML takes 450.2 kB which makes up the majority of the site volume.
Potential reduce by 414.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. This page needs HTML code to be minified as it can gain 129.2 kB, which is 29% 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 414.1 kB or 92% of the original size.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 21 (23%)
91
70
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EPAM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
epam.am
32 ms
www.epam.com
69 ms
main.min.6fe5d4427361a4c0ca5a75457e3e4256.css
33 ms
epam-core-external.min.f60768707f633383ec5b8514ab422c2e.css
34 ms
epam-core-internal.min.9f753ddec46ce6a2b876d78bbc71ff31.css
43 ms
epam-core-modules.min.a44bc9629e9e7d632f2c3ccb272e4fdc.js
50 ms
epam-com-landing23-components.min.66f50dc7737a568d3203bff16eabfc12.css
52 ms
main.min.b4994788cf1eaeed300a0aa7af53f3c8.css
41 ms
jquery.min.f65891607efbe75b84a8031849cec6c7.js
42 ms
utils.min.308082b4c347f4fec37ffef277d39d0e.js
49 ms
granite.min.d9075d4175ab7b0e3ccf4305a4089645.js
84 ms
jquery.min.dd9b395c741ce2784096e26619e14910.js
84 ms
shared.min.e9d9a3990d7779c2e8e3361187f3d36b.js
86 ms
main.min.be53d5d2acc50492007c4929cbe3ee9e.js
84 ms
contexthub.kernel.js
92 ms
epam-com-theme-switcher.min.53b5951d5f7bec085ef8dd3c23a893b2.js
84 ms
nnk8kqn.js
194 ms
api.js
85 ms
epam-core-elastic-apm.min.2195b0adc1519de2ff342e4a6d01464e.js
174 ms
epam-core-external.min.a34e5eb8659d4dbc4ab96cde5379039f.js
167 ms
epam-core-internal.min.6c543d8556914d5300ea568126fdeab4.js
160 ms
dust-templates.min.190bd37eda1541929fc39745a3acbbbf.js
162 ms
epam-com-landing23-components.min.9085028712263ce7b89ca566fd04d0ba.js
167 ms
token.json
109 ms
contexthub.pagedata.json
451 ms
segments.seg.js
432 ms
geolocation
440 ms
logo-print.png
435 ms
epam.svg
436 ms
epam_logo_light.svg
434 ms
cbr2024-cs.jpg
562 ms
a_call_to_action_for_generative_ai_cs_4.jpg
437 ms
epam_signs_strategic_collaboration_agreement_with_aws_1920.jpg
560 ms
GC_pr.jpg
557 ms
canadian_tire_corporation_and_microsoft_partner_to_advance_retail_innovation_in_canada_1920.jpg
555 ms
grain_cs.jpg
557 ms
epic.jpg
562 ms
pricelines_cs.jpg
565 ms
image.jpg
562 ms
image.jpg
565 ms
image.png
568 ms
Canada_305x314.jpg
563 ms
Colombia_305x314.jpg
564 ms
dominican_republic.jpg
565 ms
Mexico_305x314.jpg
569 ms
USA_305x314.jpg
571 ms
Armenia_305x314.jpg
570 ms
Austria_305x314.jpg
572 ms
Belarus_305x314.jpg
574 ms
Brussels.jpg
575 ms
Bulgaria_305x314.jpg
574 ms
Croatia_305x314.jpg
575 ms
Czech_Republic_305x314.jpg
575 ms
france_paris_305x314.png
574 ms
tbilisi_305x314.jpg
575 ms
Germany_305x314.jpg
568 ms
Athens_greece.jpg
570 ms
Hungary_305x314.jpg
570 ms
Ireland_305x314.jpg
559 ms
gtm.js
847 ms
257x267_EPAM_Cities_Israel.png
414 ms
Italy_305x314.jpg
403 ms
Kazakhstan_305x314.jpg
402 ms
riga.jpg
399 ms
Lithuania_305x314.jpg
398 ms
malta_305x314.jpg
397 ms
montenegro_country.jpg
404 ms
d
377 ms
d
393 ms
d
470 ms
d
472 ms
d
472 ms
sourcesanspro-light.woff
472 ms
d
394 ms
d
566 ms
d
471 ms
d
471 ms
recaptcha__en.js
561 ms
p.gif
621 ms
sourcesanspro-regular.woff
354 ms
sourcesanspro-bold.woff
356 ms
Netherlands_305x314.jpg
351 ms
Poland_305x314.jpg
281 ms
Lisbon.jpg
353 ms
romania_305x314.jpg
352 ms
Spain-Malaga-305x314.jpg
351 ms
Sweden_305x314.jpg
353 ms
Switzerland_305x314.jpg
354 ms
Ukraine_305x314.jpg
353 ms
UAE_305x314.jpg
352 ms
UK_305x314.jpg
434 ms
usbekistan_305x314.jpg
348 ms
Australia_305x314.jpg
433 ms
China_305_314.jpg
433 ms
Hong_Kong_305x314.jpg
431 ms
India_305x314.jpg
428 ms
Japan_305x314.jpg
430 ms
Malaysia_305.jpg
429 ms
Singapore_305x314.jpg
430 ms
vietnam_305x314.jpg
426 ms
Blur_Background_70.jpg
429 ms
sprite-redesign_21.svg
491 ms
sprite-redesign_21.svg
498 ms
sprite-redesign_21.svg
426 ms
sprite-redesign_21.svg
442 ms
epam.am 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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
epam.am 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
epam.am 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epam.am 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 Epam.am 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.
epam.am
Open Graph data is detected on the main page of EPAM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: