6.9 sec in total
158 ms
4.7 sec
2 sec
Visit epam.hu now to see the best up-to-date EPAM content for Hungary and also check out these interesting facts you probably never knew about epam.hu
EPAM in Hungary provides the opportunity for you to work with leading global companies across multiple industries. Join our team of innovative technologists and creative thinkers.
Visit epam.huWe analyzed Epam.hu page load time and found that the first response time was 158 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
epam.hu performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value10.1 s
0/100
25%
Value23.4 s
0/100
10%
Value24,150 ms
0/100
30%
Value0.33
34/100
15%
Value36.7 s
0/100
10%
158 ms
1333 ms
180 ms
92 ms
75 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Epam.hu, 61% (52 requests) were made to Careers.epam.hu and 20% (17 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Careers.epam.hu.
Page size can be reduced by 288.2 kB (80%)
360.0 kB
71.8 kB
In fact, the total size of Epam.hu main page is 360.0 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 321.1 kB which makes up the majority of the site volume.
Potential reduce by 287.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. This page needs HTML code to be minified as it can gain 78.9 kB, which is 25% 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 287.8 kB or 90% of the original size.
Potential reduce by 362 B
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 30 (47%)
64
34
The browser has sent 64 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 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
epam.hu
158 ms
careers.epam.hu
1333 ms
nnk8kqn.js
180 ms
main.min.6fe5d4427361a4c0ca5a75457e3e4256.css
92 ms
epam-core-external.min.f60768707f633383ec5b8514ab422c2e.css
75 ms
epam-core-internal.min.ed6a0f4a5e7f879070291844b10c46d7.css
78 ms
epam-core-components.min.cfe8482dfc1ba106e48d6e0308155554.css
82 ms
epam-core-modules.min.a44bc9629e9e7d632f2c3ccb272e4fdc.js
55 ms
epam-com-components.min.b7b2d5c5b5ca7adca882e782a89bade4.css
54 ms
main.min.b4994788cf1eaeed300a0aa7af53f3c8.css
91 ms
jquery.min.8e23e5ad8c1b5c588cca8d71df0aef0b.js
86 ms
utils.min.308082b4c347f4fec37ffef277d39d0e.js
79 ms
granite.min.d9075d4175ab7b0e3ccf4305a4089645.js
89 ms
jquery.min.dd9b395c741ce2784096e26619e14910.js
88 ms
shared.min.d8eee0685f08a5253a1d753a2619a08f.js
116 ms
main.min.389fe618ce999edba5773cfbe96a5adb.js
88 ms
contexthub.kernel.js
118 ms
api.js
117 ms
epam-core-external.min.253e065bb1bb576e8eb63c9b64b44866.js
94 ms
epam-core-internal.min.137ae8da4f0f9e430d0dea1d46dbc78d.js
92 ms
epam-core.dust.min.96d23e9e5cf550081899a8dfe1571065.js
91 ms
epam-com.dust.min.1429ab4566a4fabf53587981142d7ec3.js
95 ms
epam-core-components.min.05fcd6e1f806e4a23cc16041c6e55bb1.js
95 ms
epam-com-components.min.956062fbb4b033f2748f7a4bd1b052b4.js
106 ms
token.json
244 ms
contexthub.pagedata.json
56 ms
segments.seg.js
70 ms
geolocation
63 ms
logo-print.png
36 ms
logo_white-blue.svg
37 ms
Richard_Oliver_Legendi_500x390_dark.jpg
143 ms
Laszlo-Tarsoly-Net-Engineers.jpg
141 ms
Andras-Hargitai-DevOps-Engineers.jpg
147 ms
Horvath-Balint-BA.jpg
143 ms
Katalin_Kiss_500x390.jpg
145 ms
Eszter-Lenard-QA.jpg
144 ms
Adam_Kruppa_500x390_2.jpg
328 ms
Gyula_Sipos_500x390_1.jpg
328 ms
Program_Managers_500x390.jpg
329 ms
Homepage_mid_1920.jpg
332 ms
epam_with_open_source_solutions_for_all_areas_of_the_industry_1200.jpg
146 ms
20232080_1822284737812452_6445747601559892381_o.jpg
344 ms
Acquisitions-2.jpg
342 ms
Awards-1.jpg
332 ms
EPAMContinuum_Logo_White-Vertical-RGB.svg
328 ms
Footer-Telescope.svg
332 ms
Footer-InfoNgen.svg
336 ms
TestIO.svg
338 ms
EPAM_Anywhere_LOGO_White.svg
345 ms
gtm.js
312 ms
sourcesanspro-regular.woff
305 ms
sourcesanspro-light.woff
303 ms
sourcesanspro-bold.woff
303 ms
recaptcha__en.js
299 ms
elastic-apm-rum.umd.js
296 ms
sprite-redesign_8.svg
212 ms
diagonal-pattern.png
222 ms
d
203 ms
d
914 ms
d
915 ms
d
1056 ms
d
1056 ms
analytics.js
791 ms
conversion_async.js
788 ms
insight.min.js
971 ms
fbevents.js
1044 ms
OtAutoBlock.js
652 ms
d
289 ms
d
289 ms
d
288 ms
d
287 ms
d
287 ms
d
515 ms
d
432 ms
d
432 ms
d
431 ms
d
513 ms
d
515 ms
p.gif
724 ms
585 ms
collect
270 ms
2736293106659656
222 ms
collect
238 ms
37 ms
22 ms
epam.hu accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
epam.hu 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
epam.hu 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
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 Epam.hu 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.hu 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.hu
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: