6.2 sec in total
1.2 sec
4.4 sec
646 ms
Click here to check amazing Centertel content for Poland. Otherwise, check out these important facts you probably never knew about centertel.pl
Telefonia komórkowa i stacjonarna, internet domowy i mobilny, telewizja i więcej. Poznaj ofertę Orange i sprawdź nasze korzyści z łączenia usług w pakiety.
Visit centertel.plWe analyzed Centertel.pl page load time and found that the first response time was 1.2 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
centertel.pl performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value8.3 s
2/100
25%
Value11.2 s
5/100
10%
Value5,380 ms
0/100
30%
Value0.021
100/100
15%
Value25.2 s
0/100
10%
1150 ms
699 ms
464 ms
557 ms
341 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Centertel.pl, 3% (3 requests) were made to Sdk.privacy-center.org and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Orange.pl.
Page size can be reduced by 334.2 kB (16%)
2.2 MB
1.8 MB
In fact, the total size of Centertel.pl main page is 2.2 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. 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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 283.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. 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 283.1 kB or 86% of the original size.
Potential reduce by 91 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. Centertel images are well optimized though.
Potential reduce by 51.0 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 51.0 kB or 17% of the original size.
Potential reduce by 0 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.
Number of requests can be reduced by 55 (56%)
98
43
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Centertel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and as a result speed up the page load time.
www.orange.pl
1150 ms
ruxitagentjs_ICA7NVfghqrtux_10287240325103108.js
699 ms
7e0c4c256ffaf6ee.css
464 ms
polyfills-c67a75d1b6f99dc8.js
557 ms
vendors-node_modules_react-hook-form_dist_index_esm_mjs-1a4f30d22a75395a.js
341 ms
vendors-node_modules_lodash_isEqual_js-node_modules_lodash_isNaN_js-node_modules_xstate_lib_a-eed125-0823145f92843787.js
350 ms
vendors-node_modules_emotion_react_dist_emotion-react_browser_esm_js-node_modules_lodash_sort-bf48f7-f9fe39e461b58a12.js
361 ms
vendors-node_modules_lodash_capitalize_js-node_modules_lodash_difference_js-node_modules_loda-faf878-ee9eec146106774e.js
458 ms
vendors-node_modules_react-aria_listbox_dist_import_mjs-node_modules_react-aria_select_dist_i-34e494-be4ace7838c8185c.js
467 ms
vendors-node_modules_react-day-picker_dist_index_esm_js-node_modules_date-fns_locale_pl_mjs-7adb41597e16a1c6.js
596 ms
vendors-node_modules_react-google-recaptcha_lib_esm_index_js-node_modules_rifm_dist_rifm_esm_js-442ffbfc77ea4c63.js
573 ms
vendors-node_modules_radix-ui_react-accordion_dist_index_module_js-5bfa9d9616529e30.js
577 ms
vendors-node_modules_next_script_js-node_modules_qrcode_react_lib_esm_index_js-0c34de363db698de.js
587 ms
vendors-node_modules_xstate_react_es_useActor_js-node_modules_keen-slider_react_js-node_modul-6ca982.87315b3a5f211cda.js
673 ms
libs_components_src_Actions_ActionTrigger_tsx-a8b8349151edcd76.js
689 ms
libs_icons_src_orangeGuyIconsMap_tsx-de2d8b2b19069958.js
846 ms
libs_components_src_WWTForm_useWWTFormActions_tsx-libs_ui_Autocomplete_Autocomplete_tsx-libs_-10923b-a9361e45eb2998d4.js
839 ms
libs_components_src_WWTForm_WWTForm_tsx-6408daf17bc188e0.js
837 ms
libs_components_src_Banner_Banner_tsx-1ead1b471def0ffa.js
846 ms
libs_api_cart_src_fetchInstallmentVariants_ts-libs_api_cart_src_updateProducts_ts-libs_enhanc-171113-4b753828ce5e053d.js
845 ms
libs_virtuoso_ui_index_tsx-78e97b3520d3402b.js
992 ms
libs_components_src_Article_Article_tsx-libs_components_src_ArticleList_ArticleList_tsx-libs_-4090f3-f287d9c678b333ea.js
994 ms
libs_api_cbs_src_fetchRedirect_ts-libs_api_client_src_postForm_ts-libs_api_offer_src_fetchAdd-404b89-23ae18612d75ef45.js
847 ms
libs_components_src_TvPackages_TvPackages_tsx-cda6b9cf4110ae31.js
996 ms
libs_api_offer_src_helpers_isConvergentOfferType_ts-libs_cart_src_components_DetailsShelf_ind-295fa0-e602c087067b230c.js
996 ms
libs_ui_Form_BankAccountNumberField_tsx-libs_ui_Form_MobilePhoneNumberField_tsx-libs_ui_Form_-62ec4e-5aa9047874e2e3cb.js
992 ms
libs_components_src_OfferSelectorFilters_ConvergentOfferSelectorFilters_tsx-libs_components_s-1c9886-b9a815b44b3f2da9.js
998 ms
libs_components_src_Carousel_index_tsx-libs_components_src_Dispositions_BundleDescriptionComp-ed02bb-369b854f533f0c78.js
1119 ms
libs_components_src_AimForm_index_tsx-dba9791cee503d6f.js
1182 ms
libs_components_src_RefundForm_RefundForm_tsx-8deab4a8f0fb1772.js
1180 ms
libs_components_src_FtthForm_index_tsx-2470c360218cbb64.js
1183 ms
libs_api_offer_src_helpers_getAdditionalPackagesStatus_ts-libs_components_src_Breadcrumbs_Bre-cd1079-b1abc1489898f56e.js
1182 ms
libs_components_index_ts.ee15f8a80d232279.js
1356 ms
node_modules_lodash_includes_js-libs_components_src_Package_DeliveryPackage_index_tsx-libs_co-459a16.efa86877988fb1ad.js
1191 ms
webpack-1731679e9d716fdd.js
1344 ms
framework-69a3296573d7652f.js
1524 ms
main-a572c444d88daaff.js
1329 ms
_app-ef6eaba532011373.js
1613 ms
vendors-libs_ui_node_modules_emotion_styled_dist_emotion-styled_browser_esm_js-node_modules_s-895756-cd6a78cd2e089682.js
1014 ms
libs_contents_src_ContentsNSG_tsx-16f56a861587a5fe.js
1229 ms
index-16710d32307f8590.js
1137 ms
_buildManifest.js
1129 ms
_ssgManifest.js
1127 ms
loader.js
638 ms
gtm.js
214 ms
gtm.js
280 ms
4109370396.svg
825 ms
sprite.c424770a.svg
1409 ms
Frame-15778.png
974 ms
BannerCard-x2.jpg
976 ms
hero-mobile-x2-xiaomi.jpg
976 ms
hero-mobile-x2.jpg
973 ms
hero-mobile-x2.jpg
1184 ms
synerise-javascript-sdk.min.js
75 ms
yourcx.min.js
1133 ms
hero-mobile-x2.jpg
1204 ms
hero-mobile-x2.jpg
1152 ms
HelvNeue75_W1G.woff
1109 ms
HelvNeue55_W1G.woff
1211 ms
mob.jpg
1353 ms
hero-mobile.jpg
1231 ms
BannerCardLandscape-x2-mobile.jpg
1229 ms
BannerCard-x2.jpg
1273 ms
BannerCard-x2.jpg
1262 ms
BannerCard-x2.jpg
1262 ms
BannerCardSquare-x2.jpg
1259 ms
Banner-mobile.jpg
1504 ms
js
108 ms
analytics.js
246 ms
quantum-orangepl.js
633 ms
fbevents.js
183 ms
BannerCardSquare-x2.jpg
1269 ms
bat.js
373 ms
cookie.min.js
885 ms
BannerCardSquare-x2.jpg
1120 ms
BannerCardSquare-x2.jpg
1122 ms
Slider-mobile.jpg
1120 ms
BannerCardSquare-x2.jpg
1308 ms
BannerCard-x2.jpg
1227 ms
BannerCard-x2.jpg
1229 ms
1563724013774381
248 ms
genesys.inst.loader.js
1114 ms
sdk.7f958a3af9bbad8f0189d58c4e209f86365ada31.js
12 ms
BannerCard-x2.jpg
1152 ms
BannerCard-x2-3-.jpg
1182 ms
samsung.png
1016 ms
ui-gdpr-pl-web.7f958a3af9bbad8f0189d58c4e209f86365ada31.js
20 ms
Apple.jpg
1000 ms
logo-xiaomi-new.png
1023 ms
logo-motorola-nowe.png
1030 ms
logooppo.-new.png
1066 ms
honor.jpg
1073 ms
BannerCard-x2.jpg
1078 ms
BannerCard-x2-v2.jpg
969 ms
BannerCard-x2-5-.jpg
991 ms
BannerCard-x2-1-.jpg
1002 ms
pb-banner-sg.png
1263 ms
flex.jpg
832 ms
mo.jpg
810 ms
oferta-na-karte.jpg
841 ms
yourcx.alytics.min.html
595 ms
wc.closer.inst.js
124 ms
centertel.pl 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.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
centertel.pl 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
centertel.pl 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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centertel.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Centertel.pl 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.
centertel.pl
Open Graph description is not detected on the main page of Centertel. 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: