4.1 sec in total
408 ms
3 sec
687 ms
Visit rom1.ir now to see the best up-to-date Rom 1 content for Iran and also check out these interesting facts you probably never knew about rom1.ir
مرجع تخصصی تلفن همراه
Visit rom1.irWe analyzed Rom1.ir page load time and found that the first response time was 408 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
rom1.ir performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.7 s
57/100
25%
Value6.2 s
44/100
10%
Value200 ms
89/100
30%
Value0.008
100/100
15%
Value7.8 s
44/100
10%
408 ms
25 ms
162 ms
165 ms
166 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 94% of them (116 requests) were addressed to the original Rom1.ir, 2% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (983 ms) belongs to the original domain Rom1.ir.
Page size can be reduced by 596.2 kB (26%)
2.3 MB
1.7 MB
In fact, the total size of Rom1.ir main page is 2.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. 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 119.2 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 119.2 kB or 86% of the original size.
Potential reduce by 83.5 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. Rom 1 images are well optimized though.
Potential reduce by 393.5 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 393.5 kB or 69% of the original size.
Number of requests can be reduced by 38 (34%)
112
74
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rom 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
rom1.ir
408 ms
css
25 ms
61816fa3675544b093eb245aeddadbb3.css
162 ms
337bd261227eae2332a5c6a90095f341.css
165 ms
2218f0ea4f15c8c16e0f80ec94798442.css
166 ms
30b2d3afae7396a52a6cd96f1256bd78.css
171 ms
6ccfb4dd88668ee3a268fcfc468c638d.css
245 ms
f8468ca0ee11ba2b985b82221e7c06da.css
238 ms
b4e7bfb93e04cfee5d888ec038696c55.css
241 ms
c1591e2cc7dbb9cad692fca280957aab.css
243 ms
rom1.ir
983 ms
jquery.js
400 ms
jquery-migrate.min.js
313 ms
cf7-styles.js
318 ms
iphorm.js
319 ms
sdm_wp_scripts.js
321 ms
wp-ajaxify-comments.min.js
472 ms
kaltura.js
397 ms
jquery.cycle.all.min.js
398 ms
a
9 ms
jquery.form.min.js
328 ms
scripts.js
408 ms
dot_irecommendthis.js
408 ms
swfupload.min.js
408 ms
jquery.iphorm.js
409 ms
jquery.smooth-scroll.min.js
480 ms
jquery.qtip.min.js
490 ms
jquery.fancybox-1.3.4.pack.js
490 ms
jquery.infieldlabel.min.js
490 ms
core.min.js
490 ms
datepicker.min.js
559 ms
visualcaptcha.jquery.js
571 ms
visualcaptcha.bootstrap.js
568 ms
tie-scripts.js
646 ms
ilightbox.packed.js
569 ms
validation.js
638 ms
comment-reply.min.js
652 ms
search.js
654 ms
jquery.nivo.slider.pack.js
655 ms
jquery.cycle.all.js
636 ms
wp-emoji-release.min.js
536 ms
body-bg43.png
86 ms
head.png
522 ms
%D9%86%D9%88%D8%B1%D9%88%D8%B2.jpg
520 ms
banner1.gif
86 ms
shop-1.jpg
197 ms
update-okkkk.jpg
196 ms
UPDATE-PACK.jpg
512 ms
9192828345.jpg
517 ms
11111.png
566 ms
UNOCK.jpg
518 ms
serial.jpg
521 ms
setools.jpg
642 ms
4_251278526236327944.gif
564 ms
3333333.png
565 ms
22222.gif
637 ms
Baner-468-60-2.gif
563 ms
jpg1
642 ms
rom.jpg
645 ms
ersal.jpg
645 ms
TELEGRAMCHANEL.gif
646 ms
loading.gif
690 ms
k1xuy2AQ8wbv_amiU4s58z8E0i7KZn-EPnyo3HZu7kw.woff
12 ms
fontawesome-webfont.woff
792 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
11 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
11 ms
BebasNeue-webfont.woff
695 ms
stripe.png
684 ms
bigtheme-BShiraz.woff
661 ms
bigtheme-BYekan2.woff
717 ms
s.gif
69 ms
bigtheme-BFerdosi.woff
759 ms
logo.aspx
693 ms
10-crack-box-310x165.jpg
313 ms
frp-lock-310x165.jpg
409 ms
REMOVA-GMAIL-FROM-HUAWEI-660x330-310x165.jpg
409 ms
CERT-SAMSUNG-310x165.jpg
407 ms
My-Xperia-Theft-Protection-MXTP-310x165.jpg
526 ms
ERROR-FLASH-TOOLS-SONY-310x165.jpg
452 ms
ERROR-FLASH-TOOLS-310x165.jpg
459 ms
PIT-310x165.jpg
459 ms
LG-G4-ACCOUNT-310x165.jpg
460 ms
VIROUS-310x165.jpg
611 ms
supersu-310x165.jpg
611 ms
DELETE-GMAIL-310x165.jpg
535 ms
15555-310x165.jpg
536 ms
UNROOT-310x165.jpg
537 ms
Navitel-Navigator--310x165.jpg
681 ms
sygic1-310x165.jpg
692 ms
not-registered-on-network-310x165.png
693 ms
universal-android-flasher-310x165.jpg
616 ms
Android-World-Multitool-310x165.jpg
730 ms
samsung_galaxy_s3_neo_1n-310x165.jpg
642 ms
dr.fone_-310x165.jpeg
651 ms
trans-310x165.jpg
715 ms
jurassic_final--310x165.jpg
800 ms
4G-310x165.jpg
653 ms
not-registered-on-network-cover-310x165.jpg
651 ms
rvl.rozblog.com_-310x165.jpg
653 ms
Signal.Booster.Pro_.Android-1-310x165.jpg
713 ms
dr.web_-310x165.jpg
718 ms
Untitled-310x165.jpg
723 ms
wireless_security1-310x165.jpg
654 ms
SeekDroid--310x165.jpg
652 ms
How-to-Hack-Wif-310x165.gif
694 ms
10-crack-box-660x330.jpg
742 ms
Marshal-ME-310x165.jpg
627 ms
jpg-310x165.
629 ms
Core-Prime-110x75.jpg
596 ms
A-ROM-110x75.jpg
542 ms
S5_Panim_1280-110x75.jpg
603 ms
lg-g4-beat_range-shot-1-1024x683-310x165.jpg
611 ms
PADFONE-ASUS-310x165.jpg
589 ms
ZenPad_C7_1-110x75.jpg
580 ms
csm_ASUS_Transformer_Pad_Infinity-110x75.jpg
629 ms
Asus-MeMO-Pad-110x75.jpg
636 ms
zenfone-11-110x75.png
637 ms
lenovo-s90-7-874x492-310x165.jpg
575 ms
file-upload-tick.png
82 ms
captcha-refresh-icon.png
82 ms
default-loading.gif
82 ms
error.png
82 ms
success.png
83 ms
rom1.ir accessibility score
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
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rom1.ir 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
rom1.ir 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
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rom1.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Rom1.ir 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.
rom1.ir
Open Graph data is detected on the main page of Rom 1. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: